From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by dpdk.org (Postfix) with ESMTP id 8AB0BB36D for ; Thu, 21 Aug 2014 12:05:51 +0200 (CEST) Received: by mail-vc0-f181.google.com with SMTP id lf12so10322183vcb.26 for ; Thu, 21 Aug 2014 03:09:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=bJvxBqQ+eUAM0ExDnXbbSu/3Hi8S2cMEWvC0HILCCzM=; b=LcuLuw40C95SClqN8AjVPTGwPrQAVMqEmrIZAjGy8cUMJZV/QqvSbV0Fz1WU6b5U35 x0LkGbNmL4V3LRivF8h5cp+dfscIPK0hPRLNHyDtXE/py31XIcUdBe+lrlHvuG66if33 lr+197wLNRutltyE8jFsqe6L4cKpLhyFTRHWIp6oo5Sl0eZlFoRXmaJqqxmTM39OKK4W G3+dG6DdqpBcJkNcP1q0DS10LVjU+RwQHywX+ql8MIwKu5T+cLaUUek16QvnonVKyTr1 QTkFc0+JPazv2k7xZfbI38WDw7oHe0WU3VJZR4IDu1HrLnUXGZSsGMbfbcI3sb0mi6zF hR5g== MIME-Version: 1.0 X-Received: by 10.52.52.136 with SMTP id t8mr32877481vdo.21.1408615767242; Thu, 21 Aug 2014 03:09:27 -0700 (PDT) Received: by 10.221.61.1 with HTTP; Thu, 21 Aug 2014 03:09:27 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 19:09:27 +0900 Message-ID: From: BYEONG-GI KIM To: Masaru Oki , "De Lara Guarch, Pablo" , dev@dpdk.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] DPDK supported processor X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2014 10:05:51 -0000 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 : > 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 : > > 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 : >> >> > Hi >> > >> > Could you give the details why you think the l3fwd is not working >> > >> > Best regards, >> > Chae-yong >> > >> > 2014=EB=85=84 8=EC=9B=94 21=EC=9D=BC =EB=AA=A9=EC=9A=94=EC=9D=BC, BYEO= NG-GI KIM=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1=ED=95= =9C =EB=A9=94=EC=8B=9C=EC=A7=80: >> > >> > 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=3D"(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 =3D 0x5ffc00000) >> >> >> >> EAL: Ask a virtual area of 0x200000 bytes >> >> EAL: Virtual area found at 0x7ffff3e00000 (size =3D 0x200000) >> >> EAL: Ask a virtual area of 0x200000 bytes >> >> EAL: Virtual area found at 0x7ffff3a00000 (size =3D 0x200000) >> >> EAL: Requesting 12288 pages of size 2MB from socket 0 >> >> EAL: TSC frequency is ~2399998 KHz >> >> EAL: Master core 0 is ready (tid=3Df7fe9800) >> >> EAL: Core 3 is ready (tid=3Df5998700) >> >> EAL: Core 2 is ready (tid=3Df6199700) >> >> EAL: Core 1 is ready (tid=3Df699a700) >> >> 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=3D2 nb_txq=3D4... >> >> 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=3D0,0,0 PMD: To improve 1G driver performance, consider setting t= he >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=3D1,1,0 PMD: To improve 1G driver performance, consider setting t= he >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=3D2,2,0 PMD: To improve 1G driver performance, consider setting t= he >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=3D3,3,0 PMD: To improve 1G driver performance, consider setting t= he >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> >> >> Initializing port 1 ... Creating queues: nb_rxq=3D2 nb_txq=3D4... >> >> Address:0C:C4:7A:05:52:7B, txq=3D0,0,0 PMD: To improve 1G driver >> >> performance, consider setting the TX WTHRESH value to 4, 8, or 16. >> >> txq=3D1,1,0 PMD: To improve 1G driver performance, consider setting t= he >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=3D2,2,0 PMD: To improve 1G driver performance, consider setting t= he >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> txq=3D3,3,0 PMD: To improve 1G driver performance, consider setting t= he >> TX >> >> WTHRESH value to 4, 8, or 16. >> >> >> >> >> >> Initializing rx queues on lcore 0 ... rxq=3D0,0,0 >> >> Initializing rx queues on lcore 1 ... rxq=3D0,1,0 >> >> Initializing rx queues on lcore 2 ... rxq=3D1,0,0 >> >> Initializing rx queues on lcore 3 ... rxq=3D1,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=3D1 portid=3D0 rxqueueid=3D1 >> >> L3FWD: -- lcoreid=3D3 portid=3D1 rxqueueid=3D1 >> >> L3FWD: entering main loop on lcore 0 >> >> L3FWD: -- lcoreid=3D0 portid=3D0 rxqueueid=3D0 >> >> L3FWD: entering main loop on lcore 2 >> >> L3FWD: -- lcoreid=3D2 portid=3D1 rxqueueid=3D0 >> >> >> >> 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 KI= M >> >> > > 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. >> > >> > >