* DPDK supported processor
@ 2014-08-21 6:04 BYEONG-GI KIM
[not found] ` <CAEHt_JbcTEFa6K8n78e+8=cAJoeZcAGJMhqa0KnBCpeyOm3aiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[not found] ` <CAD16F236028A64DBBC0158B1636EA4510F309FC@SHSMSX104.ccr.corp.intel.com>
0 siblings, 2 replies; 11+ messages in thread
From: BYEONG-GI KIM @ 2014-08-21 6:04 UTC (permalink / raw)
To: dev-VfR2kkLFssw
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
^ permalink raw reply [flat|nested] 11+ messages in thread[parent not found: <CAEHt_JbcTEFa6K8n78e+8=cAJoeZcAGJMhqa0KnBCpeyOm3aiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: DPDK supported processor [not found] ` <CAEHt_JbcTEFa6K8n78e+8=cAJoeZcAGJMhqa0KnBCpeyOm3aiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2014-08-21 8:56 ` De Lara Guarch, Pablo [not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A44E-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: De Lara Guarch, Pablo @ 2014-08-21 8:56 UTC (permalink / raw) To: BYEONG-GI KIM, dev-VfR2kkLFssw > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of BYEONG-GI KIM > Sent: Thursday, August 21, 2014 7:04 AM > To: dev@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 ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <E115CCD9D858EF4F90C690B0DCB4D89721C6A44E-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>]
* Re: DPDK supported processor [not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A44E-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org> @ 2014-08-21 9:00 ` BYEONG-GI KIM [not found] ` <CAEHt_JboUrWfPSmzK=AXHR1J-v8kdNsXniGmxSTo01PEjQBnWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> [not found] ` <CADQQtgrXyb730robpVGfs0SoHF8rxu5tkxhjwgARV1XT+_eQ_g@mail.gmail.com> 0 siblings, 2 replies; 11+ messages in thread From: BYEONG-GI KIM @ 2014-08-21 9:00 UTC (permalink / raw) To: De Lara Guarch, Pablo, dev-VfR2kkLFssw 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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>: > > -----Original Message----- > > From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of BYEONG-GI KIM > > Sent: Thursday, August 21, 2014 7:04 AM > > To: dev-VfR2kkLFssw@public.gmane.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 > ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAEHt_JboUrWfPSmzK=AXHR1J-v8kdNsXniGmxSTo01PEjQBnWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: DPDK supported processor [not found] ` <CAEHt_JboUrWfPSmzK=AXHR1J-v8kdNsXniGmxSTo01PEjQBnWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2014-08-21 9:13 ` Masaru Oki [not found] ` <CAFLKUzLccGQsmdo5nDZht4PnYD6bkB1sipmXSpaTCmQxzc1-WQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Masaru Oki @ 2014-08-21 9:13 UTC (permalink / raw) To: BYEONG-GI KIM; +Cc: <dev-VfR2kkLFssw@public.gmane.org> Hi, What is the problem in l3fwd? link speed? 2014-08-21 18:00 GMT+09:00 BYEONG-GI KIM <kimbyeonggi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>: > 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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>: > > > > -----Original Message----- > > > From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of BYEONG-GI KIM > > > Sent: Thursday, August 21, 2014 7:04 AM > > > To: dev-VfR2kkLFssw@public.gmane.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 > > > ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAFLKUzLccGQsmdo5nDZht4PnYD6bkB1sipmXSpaTCmQxzc1-WQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: DPDK supported processor [not found] ` <CAFLKUzLccGQsmdo5nDZht4PnYD6bkB1sipmXSpaTCmQxzc1-WQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2014-08-21 9:15 ` BYEONG-GI KIM 0 siblings, 0 replies; 11+ messages in thread From: BYEONG-GI KIM @ 2014-08-21 9:15 UTC (permalink / raw) To: Masaru Oki, dev-VfR2kkLFssw Hello. Hmm, the problem is a little complicated. Actually, I'm trying to use dpdk-ovs with openstack deployment, but it seems not working correctly. I've thus been trying to keep track of the primary problem of this. I've thought my machine's hardware requirements may not be satisfied to support DPDK, but I think it is solved now. Best regards Byeong-Gi KIM 2014-08-21 18:13 GMT+09:00 Masaru Oki <m-oki-kJJssGRo5Gr08ZWpFnN8/c8NsWr+9BEh@public.gmane.org>: > Hi, > What is the problem in l3fwd? link speed? > > > 2014-08-21 18:00 GMT+09:00 BYEONG-GI KIM <kimbyeonggi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>: > > 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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>: >> >> > > -----Original Message----- >> > > From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of BYEONG-GI KIM >> > > Sent: Thursday, August 21, 2014 7:04 AM >> > > To: dev-VfR2kkLFssw@public.gmane.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 >> > >> > > ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CADQQtgrXyb730robpVGfs0SoHF8rxu5tkxhjwgARV1XT+_eQ_g@mail.gmail.com>]
[parent not found: <CADQQtgrXyb730robpVGfs0SoHF8rxu5tkxhjwgARV1XT+_eQ_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: DPDK supported processor [not found] ` <CADQQtgrXyb730robpVGfs0SoHF8rxu5tkxhjwgARV1XT+_eQ_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2014-08-21 9:17 ` BYEONG-GI KIM [not found] ` <CAEHt_Jb8gPc5cQhmH=EeypCXTKzikFg16hTWzh7F+3mP-djZ4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: BYEONG-GI KIM @ 2014-08-21 9:17 UTC (permalink / raw) To: Chae-yong Chong, dev-VfR2kkLFssw 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>: > 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>님이 작성한 메시지: > > 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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>: >> >> > > -----Original Message----- >> > > From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of BYEONG-GI KIM >> > > Sent: Thursday, August 21, 2014 7:04 AM >> > > To: dev-VfR2kkLFssw@public.gmane.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. > ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAEHt_Jb8gPc5cQhmH=EeypCXTKzikFg16hTWzh7F+3mP-djZ4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: DPDK supported processor [not found] ` <CAEHt_Jb8gPc5cQhmH=EeypCXTKzikFg16hTWzh7F+3mP-djZ4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2014-08-21 9:51 ` De Lara Guarch, Pablo 2014-08-21 10:00 ` Masaru Oki 1 sibling, 0 replies; 11+ messages in thread From: De Lara Guarch, Pablo @ 2014-08-21 9:51 UTC (permalink / raw) To: BYEONG-GI KIM, Chae-yong Chong, dev-VfR2kkLFssw Hi, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of BYEONG-GI KIM > Sent: Thursday, August 21, 2014 10:18 AM > To: Chae-yong Chong; dev@dpdk.org > Subject: Re: [dpdk-dev] DPDK supported processor > > 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. And it didn't work I assume? From what I am seeing, those ports are supported by DPDK (8086:1F41), as they are recognized by it, so that should not be the problem. Can you run testpmd and send a few packets to them? Then use, "show port stats all" and see the statistics are updated (make sure that you send valid packets :)) BR, Pablo > > Best regards > > Byeong-Gi KIM > > > 2014-08-21 18:14 GMT+09:00 Chae-yong Chong <cychong@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@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@intel.com>: > >> > >> > > -----Original Message----- > >> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of BYEONG-GI > KIM > >> > > Sent: Thursday, August 21, 2014 7:04 AM > >> > > To: dev@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. > > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: DPDK supported processor [not found] ` <CAEHt_Jb8gPc5cQhmH=EeypCXTKzikFg16hTWzh7F+3mP-djZ4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2014-08-21 9:51 ` De Lara Guarch, Pablo @ 2014-08-21 10:00 ` Masaru Oki [not found] ` <CAFLKUzJS5i2ay9HB=syzg_RPrrVpnfOXZ4f52YTu=ynoMQ5WoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 1 sibling, 1 reply; 11+ messages in thread From: Masaru Oki @ 2014-08-21 10:00 UTC (permalink / raw) To: BYEONG-GI KIM; +Cc: <dev-VfR2kkLFssw@public.gmane.org>, Chae-yong Chong 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>: > 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>: > > > 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>님이 작성한 메시지: > > > > 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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>: > >> > >> > > -----Original Message----- > >> > > From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of BYEONG-GI KIM > >> > > Sent: Thursday, August 21, 2014 7:04 AM > >> > > To: dev-VfR2kkLFssw@public.gmane.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. > > > ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAFLKUzJS5i2ay9HB=syzg_RPrrVpnfOXZ4f52YTu=ynoMQ5WoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: DPDK supported processor [not found] ` <CAFLKUzJS5i2ay9HB=syzg_RPrrVpnfOXZ4f52YTu=ynoMQ5WoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2014-08-21 10:09 ` BYEONG-GI KIM [not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A575@IRSMSX103.ger.corp.intel.com> 0 siblings, 1 reply; 11+ messages in thread From: BYEONG-GI KIM @ 2014-08-21 10:09 UTC (permalink / raw) To: Masaru Oki, De Lara Guarch, Pablo, dev-VfR2kkLFssw 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-kJJssGRo5Gr08ZWpFnN8/c8NsWr+9BEh@public.gmane.org>: > 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>: > > 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>: >> >> > 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>님이 작성한 메시지: >> > >> > 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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>: >> >> >> >> > > -----Original Message----- >> >> > > From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of BYEONG-GI KIM >> >> > > Sent: Thursday, August 21, 2014 7:04 AM >> >> > > To: dev-VfR2kkLFssw@public.gmane.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. >> > >> > > ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <E115CCD9D858EF4F90C690B0DCB4D89721C6A575@IRSMSX103.ger.corp.intel.com>]
[parent not found: <E115CCD9D858EF4F90C690B0DCB4D89721C6A583@IRSMSX103.ger.corp.intel.com>]
[parent not found: <E115CCD9D858EF4F90C690B0DCB4D89721C6A583-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>]
* Re: DPDK supported processor [not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A583-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org> @ 2014-08-21 13:17 ` De Lara Guarch, Pablo 0 siblings, 0 replies; 11+ messages in thread From: De Lara Guarch, Pablo @ 2014-08-21 13:17 UTC (permalink / raw) To: BYEONG-GI KIM, Masaru Oki, dev-VfR2kkLFssw > > From: BYEONG-GI KIM [mailto:kimbyeonggi@gmail.com] > Sent: Thursday, August 21, 2014 11:09 AM > To: Masaru Oki; De Lara Guarch, Pablo; dev@dpdk.org > Subject: Re: [dpdk-dev] DPDK supported processor > > 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... I assume you are using DPDK 1.7. DPDK-ovs team has been working on a fix for that, so you should check on their mailing list. > > Best regards > > Byeong-Gi KIM > > 2014-08-21 19:00 GMT+09:00 Masaru Oki <m-oki@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@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@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@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@intel.com>: > >> > >> > > -----Original Message----- > >> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of BYEONG-GI > KIM > >> > > Sent: Thursday, August 21, 2014 7:04 AM > >> > > To: dev@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. > > > ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAD16F236028A64DBBC0158B1636EA4510F309FC@SHSMSX104.ccr.corp.intel.com>]
[parent not found: <B6059B2012717B4390714544B1F509E110D59B4A@SHSMSX103.ccr.corp.intel.com>]
[parent not found: <B6059B2012717B4390714544B1F509E110D59B4A-0J0gbvR4kTggGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>]
* Re: DPDK supported processor [not found] ` <B6059B2012717B4390714544B1F509E110D59B4A-0J0gbvR4kTggGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org> @ 2014-08-22 5:34 ` BYEONG-GI KIM 0 siblings, 0 replies; 11+ messages in thread From: BYEONG-GI KIM @ 2014-08-22 5:34 UTC (permalink / raw) To: Cao, Min, dev-VfR2kkLFssw Dear Cao Min Thank you for the information. Best regards Byeong-Gi KIM 2014-08-22 14:30 GMT+09:00 Cao, Min <min.cao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>: > Hi Byeong-Gi KIM, > > We tested with platform as below. Pls take information below as reference. > > Cpu: Genuine Intel(R) CPU 4000 @ 2.41GHz > NIC: Niantic 82599 > Bios: EDVLCRB1.86B.0008.R00.1303061138 > OS: 3.4.18-yocto-standard(32/64 bit) or FC20 > > We validated the test cases list below: > pmd > Checksum > Ipv4frag > Hello_world > Flow director > Jumboframe and scatter > Ieee1588 > Multiprocess > Flow control > Whitelist > blacklist > vlan > > Regards, > Cao Min > > -----Original Message----- > From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of BYEONG-GI KIM > Sent: Thursday, August 21, 2014 2:04 PM > To: dev-VfR2kkLFssw@public.gmane.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 > > ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2014-08-22 5:34 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-21 6:04 DPDK supported processor BYEONG-GI KIM
[not found] ` <CAEHt_JbcTEFa6K8n78e+8=cAJoeZcAGJMhqa0KnBCpeyOm3aiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-21 8:56 ` De Lara Guarch, Pablo
[not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A44E-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-21 9:00 ` BYEONG-GI KIM
[not found] ` <CAEHt_JboUrWfPSmzK=AXHR1J-v8kdNsXniGmxSTo01PEjQBnWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-21 9:13 ` Masaru Oki
[not found] ` <CAFLKUzLccGQsmdo5nDZht4PnYD6bkB1sipmXSpaTCmQxzc1-WQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-21 9:15 ` BYEONG-GI KIM
[not found] ` <CADQQtgrXyb730robpVGfs0SoHF8rxu5tkxhjwgARV1XT+_eQ_g@mail.gmail.com>
[not found] ` <CADQQtgrXyb730robpVGfs0SoHF8rxu5tkxhjwgARV1XT+_eQ_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-21 9:17 ` BYEONG-GI KIM
[not found] ` <CAEHt_Jb8gPc5cQhmH=EeypCXTKzikFg16hTWzh7F+3mP-djZ4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-21 9:51 ` De Lara Guarch, Pablo
2014-08-21 10:00 ` Masaru Oki
[not found] ` <CAFLKUzJS5i2ay9HB=syzg_RPrrVpnfOXZ4f52YTu=ynoMQ5WoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-21 10:09 ` BYEONG-GI KIM
[not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A575@IRSMSX103.ger.corp.intel.com>
[not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A583@IRSMSX103.ger.corp.intel.com>
[not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C6A583-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-21 13:17 ` De Lara Guarch, Pablo
[not found] ` <CAD16F236028A64DBBC0158B1636EA4510F309FC@SHSMSX104.ccr.corp.intel.com>
[not found] ` <B6059B2012717B4390714544B1F509E110D59B4A@SHSMSX103.ccr.corp.intel.com>
[not found] ` <B6059B2012717B4390714544B1F509E110D59B4A-0J0gbvR4kTggGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-22 5:34 ` BYEONG-GI KIM
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.