From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 0904AC30A for ; Fri, 5 Feb 2016 15:58:47 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga103.jf.intel.com with ESMTP; 05 Feb 2016 06:58:47 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,401,1449561600"; d="scan'208";a="741151752" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga003.jf.intel.com with ESMTP; 05 Feb 2016 06:58:46 -0800 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.100]) by IRSMSX101.ger.corp.intel.com ([169.254.1.113]) with mapi id 14.03.0248.002; Fri, 5 Feb 2016 14:58:45 +0000 From: "Pattan, Reshma" To: Thomas Monjalon Thread-Topic: [PATCH v3 0/3] fix RTE_PROC_PRIMARY_OR_ERR_RET RTE_PROC_PRIMARY_OR_RET Thread-Index: AQHRR9cPs3TocqDs2UekvRgpjBoSeJ8dY4+AgAAaspA= Date: Fri, 5 Feb 2016 14:58:44 +0000 Message-ID: <3AEA2BF9852C6F48A459DA490692831FFBEB1B@IRSMSX109.ger.corp.intel.com> References: <1450873172-21932-1-git-send-email-reshma.pattan@intel.com> <1452011698-27354-1-git-send-email-reshma.pattan@intel.com> <8174506.yrx6lfkTWS@xps13> In-Reply-To: <8174506.yrx6lfkTWS@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNDVkZmMwZTctYWZiYi00YjI1LWJiMTUtNjJlZjBiZTBjMDYwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiUTVNeGNkUEtzVFVjMVVXZkd6YUo0MXFJMFJadmRRSkFsZ3lUSG1tQmJwTT0ifQ== x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v3 0/3] fix RTE_PROC_PRIMARY_OR_ERR_RET RTE_PROC_PRIMARY_OR_RET 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, 05 Feb 2016 14:58:48 -0000 Hi Thomas, > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Friday, February 5, 2016 9:43 AM > To: Pattan, Reshma > Cc: Ananyev, Konstantin; Doherty, Declan; dev@dpdk.org; Qiu, Michael > Subject: Re: [PATCH v3 0/3] fix RTE_PROC_PRIMARY_OR_ERR_RET > RTE_PROC_PRIMARY_OR_RET >=20 > Hi, >=20 > 2016-01-05 16:34, Reshma Pattan: > > From: reshmapa > > > > Patches 1 and 2 removes RTE_PROC_PRIMARY_OR_ERR_RET and > > RTE_PROC_PRIMARY_OR_RET macro usage from rte_ether and rte_cryptodev > > libraries to allow API access to secondary process. >=20 > I don't understand the use case. These changes were added for the use case where vdev has to be configured f= rom secondary process. As of now, secondary process is allowed to create vdev but not allowed to = configure it. Ex1: tcpdump feature needs these changes. As we create & configure vdev fro= m secondary process. Ex2: Sean Harte, initially reported this as limitation as part of his devel= opment related to containers proof-of concept.=20 > What is the role of the primary process if queues are configured by the > secondary process? There can be use cases where primary and secondary processes needs to conf= igure different queues of same port or needs to configure different PCI por= ts. I assume, users will be aware of PCI port & queue combinations used in prim= ary and will not try to reconfigure them in secondary. > You have not answered to Michael: > http://dpdk.org/ml/archives/dev/2015-December/030811.html >=20 > Other question first asked by Michael > http://dpdk.org/ml/archives/dev/2015-December/030777.html > There are some comments asserting that it is not safe for secondary. > And your answer was it is safe for vdev? And what about PCI devices? I assume, users will be aware of PCI port & queue combinations used in prim= ary and will not try to reconfigure them in secondary. Thanks, Reshma