From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 78AD46930 for ; Wed, 2 Apr 2014 17:41:39 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 02 Apr 2014 08:33:54 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,780,1389772800"; d="scan'208";a="505397653" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by fmsmga001.fm.intel.com with ESMTP; 02 Apr 2014 08:33:52 -0700 Received: from irsmsx105.ger.corp.intel.com (163.33.3.28) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 2 Apr 2014 16:33:09 +0100 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.172]) by IRSMSX105.ger.corp.intel.com ([169.254.7.87]) with mapi id 14.03.0123.003; Wed, 2 Apr 2014 16:33:09 +0100 From: "Richardson, Bruce" To: Mauro Annarumma , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Issues on FDIR and multi-processes Thread-Index: AQHPToTg0s2Tvw87A0i4succYo0NNZr+cu1g Date: Wed, 2 Apr 2014 15:33:09 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B01A9F7CAC@IRSMSX103.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Issues on FDIR and multi-processes 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: Wed, 02 Apr 2014 15:41:39 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mauro Annarumma > Sent: Wednesday, April 02, 2014 4:02 PM > To: dev@dpdk.org > Subject: [dpdk-dev] Issues on FDIR and multi-processes >=20 > Hi everyone, > we are working with Flow DIRector on a multiprocess application. This app= lication consists of N secondary processes,=20 > each one receiving packets directly from its own queue on the NIC. It wor= ks fine when each secondary process runs on > a different CPU core; instead, if we try to run two secondary processes o= n the same CPU core, these processes aren't=20 > able to read from their respectively queue. Running two co-operating Intel DPDK processes on the same lcore is not a su= pported configuration of Intel DPDK multiprocess. [Please see section 20.3 = of the Intel DPDK Programmer's Guide document, which lists out some limitat= ions of multi-process support]. Basically, each process in a multiprocess c= onfiguration is equivalent to a thread in a normal application deployment, = so just as having two threads on the same core causes problems with mempool= s and other objects which use an "lcore_id" value unique in each thread to = work correctly, so running two processes on the same lcore can cause exactl= y the same issues.=20 If you really do want to use this model and have multiple threads on the sa= me lcore, at minimum you need to ensure that each thread/process has a uniq= ue lcore_id value <=3D RTE_MAX_LCORE. /Bruce