It works fine with DPDK at least. The problem is that OVDK, especially ovs-dpdk command supported by the OVDK, doesn't work correctly. I tested the DPDK application, l3fwd, in order to know where the incorrect operation comes from, either DPDK or OVDK itself. And I know now the issue seems belonging to OVDK. :) In the OVDK, the physical ports even could not detected...
Best regards Byeong-Gi KIM 2014-08-21 19:00 GMT+09:00 Masaru Oki <m-oki at stratosphere.co.jp>: > I have SUPERMICRO A1SRi-2758F mainboard (onboard Atom C2758), > and onboard NICs work fine with DPDK application. > > 2014-08-21 18:17 GMT+09:00 BYEONG-GI KIM <kimbyeonggi at gmail.com>: > > Well, I did think that the NIC in my testing machine may not support DPDK >> rather than thinking l3fwd is not working. >> >> I just tested the l3fwd sample application to identify whether the NIC >> supports DPDK or not. >> >> Best regards >> >> Byeong-Gi KIM >> >> >> 2014-08-21 18:14 GMT+09:00 Chae-yong Chong <cychong at gmail.com>: >> >> > Hi >> > >> > Could you give the details why you think the l3fwd is not working >> > >> > Best regards, >> > Chae-yong >> > >> > 2014? 8? 21? ???, BYEONG-GI KIM<kimbyeonggi at gmail.com>?? ??? ???: >> > >> > Thank you for the reply. >> >> >> >> I tested l3forwarding sample application, and the results were as >> below: >> >> >> >> sudo ./build/l3fwd -c 0x0F -n 4 -- -p 0x03 >> >> --config="(0,0,0),(0,1,1),(1,0,2),(1,1,3)" >> >> 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 6 on socket 0 >> >> EAL: Detected lcore 7 as core 7 on socket 0 >> >> EAL: Support maximum 64 logical core(s) by configuration. >> >> EAL: Detected 8 lcore(s) >> >> EAL: Searching for IVSHMEM devices... >> >> EAL: No IVSHMEM configuration found! >> >> EAL: Setting up memory... >> >> EAL: Ask a virtual area of 0x5ffc00000 bytes >> >> EAL: Virtual area found at 0x2aa4aae00000 (size = 0x5ffc00000) >> >> >> >> EAL: Ask a virtual area of 0x200000 bytes >> >> EAL: Virtual area found at 0x7ffff3e00000 (size = 0x200000) >> >> EAL: Ask a virtual area of 0x200000 bytes >> >> EAL: Virtual area found at 0x7ffff3a00000 (size = 0x200000) >> >> EAL: Requesting 12288 pages of size 2MB from socket 0 >> >> EAL: TSC frequency is ~2399998 KHz >> >> EAL: Master core 0 is ready (tid=f7fe9800) >> >> EAL: Core 3 is ready (tid=f5998700) >> >> EAL: Core 2 is ready (tid=f6199700) >> >> EAL: Core 1 is ready (tid=f699a700) >> >> EAL: PCI device 0000:00:14.0 on NUMA socket -1 >> >> EAL: probe driver: 8086:1f41 rte_igb_pmd >> >> EAL: PCI memory mapped at 0x7ffff7f8d000 >> >> EAL: PCI memory mapped at 0x7ffff7f89000 >> >> EAL: PCI device 0000:00:14.1 on NUMA socket -1 >> >> EAL: probe driver: 8086:1f41 rte_igb_pmd >> >> EAL: PCI memory mapped at 0x7ffff7f69000 >> >> EAL: PCI memory mapped at 0x7ffff7f65000 >> >> EAL: PCI device 0000:00:14.2 on NUMA socket -1 >> >> EAL: probe driver: 8086:1f41 rte_igb_pmd >> >> EAL: 0000:00:14.2 not managed by UIO driver, skipping >> >> EAL: PCI device 0000:00:14.3 on NUMA socket -1 >> >> EAL: probe driver: 8086:1f41 rte_igb_pmd >> >> EAL: 0000:00:14.3 not managed by UIO driver, skipping >> >> EAL: PCI device 0000:00:14.2 on NUMA socket -1 >> >> EAL: probe driver: 8086:1f41 rte_igb_pmd >> >> EAL: 0000:00:14.2 not managed by UIO driver, skipping >> >> EAL: PCI device 0000:00:14.3 on NUMA socket -1 >> >> EAL: probe driver: 8086:1f41 rte_igb_pmd >> >> EAL: 0000:00:14.3 not managed by UIO driver, skipping >> >> Initializing port 0 ... Creating queues: nb_rxq=2 nb_txq=4... >> >> Address:0C:C4:7A:05:52:7A, Allocated mbuf pool on socket 0 >> >> LPM: Adding route 0x01010100 / 24 (0) >> >> LPM: Adding route 0x02010100 / 24 (1) >> >> LPM: Adding route IPV6 / 48 (0) >> >> LPM: Adding route IPV6 / 48 (1) >> >> txq=0,0,0 PMD: To improve 1G driver performance, consider setting the >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=1,1,0 PMD: To improve 1G driver performance, consider setting the >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=2,2,0 PMD: To improve 1G driver performance, consider setting the >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=3,3,0 PMD: To improve 1G driver performance, consider setting the >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> >> >> Initializing port 1 ... Creating queues: nb_rxq=2 nb_txq=4... >> >> Address:0C:C4:7A:05:52:7B, txq=0,0,0 PMD: To improve 1G driver >> >> performance, consider setting the TX WTHRESH value to 4, 8, or 16. >> >> txq=1,1,0 PMD: To improve 1G driver performance, consider setting the >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=2,2,0 PMD: To improve 1G driver performance, consider setting the >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=3,3,0 PMD: To improve 1G driver performance, consider setting the >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> >> >> >> >> Initializing rx queues on lcore 0 ... rxq=0,0,0 >> >> Initializing rx queues on lcore 1 ... rxq=0,1,0 >> >> Initializing rx queues on lcore 2 ... rxq=1,0,0 >> >> Initializing rx queues on lcore 3 ... rxq=1,1,0 >> >> >> >> Checking link status.................done >> >> Port 0 Link Up - speed 100 Mbps - full-duplex >> >> Port 1 Link Up - speed 100 Mbps - full-duplex >> >> L3FWD: entering main loop on lcore 1 >> >> L3FWD: entering main loop on lcore 3 >> >> L3FWD: -- lcoreid=1 portid=0 rxqueueid=1 >> >> L3FWD: -- lcoreid=3 portid=1 rxqueueid=1 >> >> L3FWD: entering main loop on lcore 0 >> >> L3FWD: -- lcoreid=0 portid=0 rxqueueid=0 >> >> L3FWD: entering main loop on lcore 2 >> >> L3FWD: -- lcoreid=2 portid=1 rxqueueid=0 >> >> >> >> Anyway, I'll also try to test the testpmd application. >> >> >> >> Best regards >> >> >> >> Byeong-Gi KIM >> >> >> >> >> >> >> >> 2014-08-21 17:56 GMT+09:00 De Lara Guarch, Pablo < >> >> pablo.de.lara.guarch at intel.com>: >> >> >> >> > > -----Original Message----- >> >> > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of BYEONG-GI KIM >> >> > > Sent: Thursday, August 21, 2014 7:04 AM >> >> > > To: dev at dpdk.org >> >> > > Subject: [dpdk-dev] DPDK supported processor >> >> > > >> >> > > Hello. >> >> > > >> >> > > I'm now using Intel Atom processor C2758 on the DPDK testing >> machines, >> >> > but >> >> > > it seems not working. >> >> > > >> >> > > Which sample application would be recommended to test the NIC >> actually >> >> > > works well with DPDK? >> >> > > >> >> > > Best regards >> >> > > >> >> > > Byeong-Gi KIM >> >> > >> >> > Hi, >> >> > >> >> > Testpmd is the best application you can use for that. >> >> > >> >> > Best regards, >> >> > Pablo >> >> > >> >> >> > >> > >> > -- >> > >> > >> > May the Fun with you. >> > >> > >
