From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 542DDB374 for ; Fri, 11 Jul 2014 04:53:14 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 10 Jul 2014 19:53:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,641,1400050800"; d="scan'208";a="541785032" Received: from fmsmsx105.amr.corp.intel.com ([10.19.9.36]) by orsmga001.jf.intel.com with ESMTP; 10 Jul 2014 19:53:12 -0700 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by FMSMSX105.amr.corp.intel.com (10.19.9.36) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 10 Jul 2014 19:53:11 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 10 Jul 2014 19:53:11 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.122]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.188]) with mapi id 14.03.0123.003; Fri, 11 Jul 2014 10:53:10 +0800 From: "Zhang, Helin" To: "Olson, Matt Lyle" , "dev@dpdk.org" Thread-Topic: Running kni with low amount of cores Thread-Index: Ac+bsbTzVYFlsn5aQ9WbmDGiTxNUeQBAO2Pg Date: Fri, 11 Jul 2014 02:53:09 +0000 Message-ID: References: <0262E9805BD2664BBA70725A838003031C86BD@G2W2432.americas.hpqcorp.net> In-Reply-To: <0262E9805BD2664BBA70725A838003031C86BD@G2W2432.americas.hpqcorp.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Running kni with low amount of cores 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: Fri, 11 Jul 2014 02:53:14 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olson, Matt Lyle > Sent: Thursday, July 10, 2014 4:12 AM > To: dev@dpdk.org > Subject: [dpdk-dev] Running kni with low amount of cores >=20 > Hello, >=20 > I have two NIC devices and a quad core system that I'm trying to run kni = on. I > would like to leave two cores for general use and two cores for kni. When= run > kni on just one of the ports, everything works fine and I can use that vE= th > normally. The exact command I run is this: ./kni -c 0x0c -n 2 -- -P -p 0x= 1 > -config=3D"(0,2,3)" But when I try to run kni on both ports, I can't find= a > configuration to make it work. Here's all the configs that I have tried, = but none > of them seem to work properly, the same way as just a single port: "(0,2,= 3), > (1,2,3)" "(0,2,3), (1,3,2)" "(0,2,2), (1,3,3)". I'm wondering if i= t is > supposed to work this way, where each port needs its own Tx and Rx core,= or > if there is a way to get around it. If it is supposed to work this way, w= ould it be > worth my time to edit the code to allow me to have all Rx information dea= lt > with on one core and all Tx on another? >=20 > Thanks, > Matt Olson Hi Matt For the KNI example application, each lcore is used for RX or TX of a port = only, you can check the first part of code in main_loop() in examples/kni/m= ain.c. It assumes that the number of lcores is not the bottle neck. So for the scenario of yours, that might be supported. But it would not be = too difficult to support your case by modifying the example application by = yourself. Regards, Helin