[dpdk-users] (no subject)

2016-05-19 Thread dawid_jurek
Hello,

Did you read this?
http://dpdk.org/doc/guides/linux_gsg/index.html

Regards,
Dawid

W dniu 2016-05-19 12:19:30 u?ytkownik THEEYAGU S  napisa?:
> Hi All,
> 
>I need to build OVS 2.5.0(openvswitch) on DPDK environment, I tried to
> install DPDK but its is failing.
> 
>   Can any one let me know  how to install DPDK.
> 
>   Below are my Linux environment.
>  Ubuntu 14.04
>  Kernel version 4.6
> 
> I am not aware on DPDK, so give me the system requirements and steps to
> install DPDK on Ubuntu 14.04, with kernel version 4.6
> 
> 
> 
> Thanks & Regards,
> Theeyagu S
> 





[dpdk-users] Error in rte_eal_init using dpdk 16.04 and Qlogic (Broadcom) bnx2x driver in a SECONDARY process

2016-05-04 Thread dawid_jurek
Hello David,

By looking on driver sources (bnx2x_ethdev.c) assertion `sc->bar[0].base_addr' 
fail is caused by pci_dev->mem_resource[0].addr == NULL. It means that MMIO 
mapping of region nr. 0 failed. 
The reason of this may be print reported on ring level some time before crash:

"EAL: memzone_reserve_aligned_thread_unsafe(): memzone 
already exists
RING: Cannot reserve memory."

I suspect some memory allocation issue but not 100% sure.

Regards,
Dawid


> Hello,
> 
> We are trying to run the
> "dpdk-16.04\examples\multi_process\client_server_mp" sample application 
> on a RHEL6.7 linux server, with DPDK 16.04 and the following network
> interfaces:
> 
> Network devices using DPDK-compatible driver
> 
> :10:00.0 'BCM57840 NetXtreme II 10 Gigabit Ethernet' drv=igb_uio
> unused=bnx2x
> :10:00.1 'BCM57840 NetXtreme II 10 Gigabit Ethernet' drv=igb_uio
> unused=bnx2x
> ===
> 
> PMD: bnx2x_print_adapter_info(): ASIC : 0x168d1010
> PMD: bnx2x_print_adapter_info():  Rev : B1
> PMD: bnx2x_print_adapter_info(): Bus PCIe : 8,
> PMD: bnx2x_print_adapter_info():5 Gbps
> PMD: bnx2x_print_adapter_info():Flags :
> PMD: bnx2x_print_adapter_info():MSI
> PMD: bnx2x_print_adapter_info(): |
> PMD: bnx2x_print_adapter_info():MSI-X
> PMD: bnx2x_print_adapter_info():   Queues :
> PMD: bnx2x_print_adapter_info():RSS : 1
> PMD: bnx2x_print_adapter_info(): DPDK : DPDK 16.04.0
> PMD: bnx2x_print_adapter_info():   Driver : BNX2X PMD 1.78.18_1.0.0
> PMD: bnx2x_print_adapter_info(): Firmware : 7.2.51
> PMD: bnx2x_print_adapter_info(): Bootcode : 7.13.24
> PMD: bnx2x_print_adapter_info():
> 
> We can run the server process, without problems, with the following command.
> 
>   ./mp_server -c 6 -n 4 -- -p 3 -n 1
> 
>  .than, in a second shell, we run the client process with the following
> command .
> 
>   ./mp_client -c 8 -n 4 --proc-type=auto -- -n 0
>   
> .and we always get this output:
> 
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Detected lcore 4 as core 4 on socket 0
> EAL: Detected lcore 5 as core 5 on socket 0
> EAL: Detected lcore 6 as core 0 on socket 1
> EAL: Detected lcore 7 as core 1 on socket 1
> EAL: Detected lcore 8 as core 2 on socket 1
> EAL: Detected lcore 9 as core 3 on socket 1
> EAL: Detected lcore 10 as core 4 on socket 1
> EAL: Detected lcore 11 as core 5 on socket 1
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 12 lcore(s)
> EAL: Auto-detected process type: SECONDARY
> EAL: Setting up physically contiguous memory...
> EAL: Analysing 16 files
> EAL: Mapped segment 0 of size 0x2
> EAL: Mapped segment 1 of size 0x2
> EAL: memzone_reserve_aligned_thread_unsafe(): memzone 
> already exists
> RING: Cannot reserve memory
> EAL: TSC frequency is ~240 KHz
> EAL: Master lcore 3 is ready (tid=f7fec880;cpuset=[3])
> PMD: rte_bnx2x_pmd_init():  >>
> PMD: rte_bnx2xvf_pmd_init():  >>
> EAL: PCI device :10:00.0 on NUMA socket 0
> EAL:   probe driver: 14e4:16a1 rte_bnx2x_pmd
> EAL:   PCI memory mapped at 0x7fffc000
> EAL:   PCI memory mapped at 0x7fffc080
> EAL:   PCI memory mapped at 0x7fffc100
> PMD: eth_bnx2x_dev_init():  >>
> PMD: bnx2x_common_dev_init():  >>
> mp_client: /root/dpdk/dpdk-16.04/drivers/net/bnx2x/bnx2x_ethdev.c:430:
> bnx2x_common_dev_init: Assertion `sc->bar[0].base_addr' failed.
> Aborted (core dumped)
> 
> and this is the call stack from dump file:
> 
> (gdb) bt
> #0  0x00363c032625 in raise () from /lib64/libc.so.6
> #1  0x00363c033e05 in abort () from /lib64/libc.so.6
> #2  0x00363c02b74e in __assert_fail_base () from /lib64/libc.so.6
> #3  0x00363c02b810 in __assert_fail () from /lib64/libc.so.6
> #4  0x004b8ed3 in bnx2x_common_dev_init ()
> #5  0x00473bfa in rte_eth_dev_init ()
> #6  0x00482422 in rte_eal_pci_probe ()
> #7  0x004779b8 in rte_eal_init ()
> #8  0x00420e7c in main ()
>   
> All this steps on different server with Intel NICs make the application
> (server side e client side) run with no problems at all.
> 
> Is there someone that could help us to understand this issue with Qlogic
> (Broadcom) driver?
> 
> Thanks in advance,
> David Coen
> 
> 
> 





[dpdk-users] EAL: No probed ethernet devices

2016-05-04 Thread dawid_jurek
Hello Upendra,

"I have bound Intel 82579V nic with
igb_uio and was working on testpmd application and i am not getting any
ports for testpmd probably beacuse of EAL: No probed ethernet devices
error."

Are you sure this device is supported by dpdk? According to NIC's list coming 
from: http://dpdk.org/doc/nics Intel 82579V is not supported by any PMD. 
To be 100% sure you may look at dpdk source code - 
dpdk/lib/librte_eal/common/include/rte_pci_dev_ids.h which doesn't contain 
82579V as well.  
Good news is that your second card - Intel 82540EM is supported by e1000 from 
dpdk.

Regards,
Dawid


W dniu 2016-05-04 16:47:26 u?ytkownik Upendra Pathrikar  napisa?:
> I am new to DPDK and running 2.2.0,I have bound Intel 82579V nic with
> igb_uio and was working on testpmd application and i am not getting any
> ports for testpmd probably beacuse of EAL: No probed ethernet devices
> error. Please let me know what i'm doing wrong.
> 
> //
> 
> Network devices using DPDK-compatible driver
> 
> :00:19.0 '82579V Gigabit Network Connection' drv=igb_uio
> unused=uio_pci_generic
> 
> Network devices using kernel driver
> ===
> :02:00.0 '82540EM Gigabit Ethernet Controller' if=eth0 drv=e1000
> unused=igb_uio,uio_pci_generic *Active*
> 
> Other network devices
> =
> 
> 
> //
> 
> -pmd$ sudo ./testpmd -c 0xf -n 4 -w 00:19.0 -- -i
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 4 lcore(s)
> EAL: VFIO modules not all loaded, skip VFIO support...
> EAL: Setting up physically contiguous memory...
> EAL: Ask a virtual area of 0x20 bytes
> EAL: Virtual area found at 0x7f4ed1e0 (size = 0x20)
> EAL: Ask a virtual area of 0x140 bytes
> EAL: Virtual area found at 0x7f4ed080 (size = 0x140)
> EAL: Ask a virtual area of 0x20 bytes
> EAL: Virtual area found at 0x7f4ed040 (size = 0x20)
> EAL: Ask a virtual area of 0x20 bytes
> EAL: Virtual area found at 0x7f4ed000 (size = 0x20)
> EAL: Ask a virtual area of 0x20 bytes
> EAL: Virtual area found at 0x7f4ecfc0 (size = 0x20)
> EAL: Ask a virtual area of 0x3e40 bytes
> EAL: Virtual area found at 0x7f4e9160 (size = 0x3e40)
> EAL: Ask a virtual area of 0x20 bytes
> EAL: Virtual area found at 0x7f4e9120 (size = 0x20)
> EAL: Ask a virtual area of 0x3fc0 bytes
> EAL: Virtual area found at 0x7f4e5140 (size = 0x3fc0)
> EAL: Ask a virtual area of 0x20 bytes
> EAL: Virtual area found at 0x7f4e5100 (size = 0x20)
> EAL: Requesting 1024 pages of size 2MB from socket 0
> EAL: TSC frequency is ~3092975 KHz
> EAL: Master lcore 0 is ready (tid=d40d7940;cpuset=[0])
> EAL: lcore 1 is ready (tid=50fff700;cpuset=[1])
> EAL: lcore 3 is ready (tid=4fffd700;cpuset=[3])
> EAL: lcore 2 is ready (tid=507fe700;cpuset=[2])
> EAL: No probed ethernet devices
> Interactive-mode selected
> Done
> testpmd> show info port all
> Bad arguments
> testpmd> show port info all
> testpmd> show port info 0
> Invalid port 0
> Valid port range is [0]
> testpmd> show port info 1
> Invalid port 1
> Valid port range is [0]
> testpmd> quit
> bye...
> 
> //
>  even i white listed specific nic , still i am getting the error
> please let me know, how to resolve this.
> 
> Thanks
> 
> -- 
> 
> 
> 
> 
> 
> *Regards,Upendra Sunil PathrikarBharti School of Telecom Technology and
> Management,Indian Institute of Technology, Delhi.*
> 





[dpdk-users] Minimal dpdk configuration for 2 hosts

2016-03-10 Thread dawid_jurek
Hello Harold,
I did investigation and one directional forwarding through 2 hosts connected by 
one port NIC each is possible indeed.
Testpmd with following command line arguments can do that:
?
On host1 (as sender):
./testpmd -c 0x3 -n4 -- -i --forward-mode=txonly --port-topology=chained
On host2 (as reciever):
./testpmd -c 0x3 -n4 -- -i --forward-mode=rxonly --port-topology=chained
?
Anyway still I don't how to run two directional communication. Harold, could 
you provide commands/command line options for this?
Also It seems that? 2 port NIC on every host is required to run basicfwd, 
rxtx_callbacks and other examples
(dpdk gives me print that number of ports must be even).
?
Regards,
Dawid
?
W dniu 2016-03-06 10:30:51 u?ytkownik Harold Demure  napisa?:
Hello Dawid,
I am no expert but a single port should be able to take care of both TX and RX 
queues. For example, I am currently running two hosts with only one port each 
and they are able to both send and receive messages.
Regards,
Harold
2016-03-04 21:47 GMT+01:00 dawid_jurek :
Hello,
I wonder what is the minimal configuration (in sense on number of NIC ports) to 
run basic dpdk examples like
basicfwd, rxtx_callbacks or forwarding by testpmd for 2 hosts connected 
directly by Ethernet.
Is it possible to perform one directional transmission for some kind of 
sender-reciever scenario (2 hosts, every host with one port)?
It seems that for every kind of transmission between 2 machines I need at least 
4 ports
(because every port may take care of TX or RX but not both of them at the same 
time).
Is it correct?
Regards,
Dawid
?


[dpdk-users] Minimal dpdk configuration for 2 hosts

2016-03-04 Thread dawid_jurek
Hello,
I wonder what is the minimal configuration (in sense on number of NIC ports) to 
run basic dpdk examples like
basicfwd, rxtx_callbacks or forwarding by testpmd for 2 hosts connected 
directly by Ethernet.
Is it possible to perform one directional transmission for some kind of 
sender-reciever scenario (2 hosts, every host with one port)?
It seems that for every kind of transmission between 2 machines I need at least 
4 ports
(because every port may take care of TX or RX but not both of them at the same 
time).
Is it correct?
Regards,
Dawid


[dpdk-users] SyntaxError in setup.sh during binding ethernet device

2016-01-19 Thread dawid_jurek


W dniu 2016-01-19 11:19:55 u?ytkownik Thomas Monjalon  napisa?:
> Hi
> 
> 2016-01-19 10:45, dawid_jurek:
> > Hello DPDK developers,
> > I experienced issue when I ran tools/setup.sh and chose option [23]: Bind 
> > Ethernet device to IGB UIO module.
> > Script Output:
> > File ".../dpdk/dpdk-2.2.0/tools/dpdk_nic_bind.py", line 113
> > """ % locals() # replace items from local variables
> >   ^
> > SyntaxError: invalid syntax
> > It turned out that python 2.7 set as default in system was needed.
> > So I added python2 to every line with dpdk_nic_bind.py call in 
> > tools/setup.sh and now it works fine.
> > But the question is: is it expected behaviour? Shouldn't it be fixed by 
> > simple patch in way I did it?
> 
> Yes a patch would be appreciated to make it python 3 friendly.
> Thanks
> 

OK. I will prepare patch for dpdk_nic_bind.py soon.
Regards,
Dawid