From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id B233D4B79 for ; Tue, 25 Oct 2016 16:32:41 +0200 (CEST) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga101.fm.intel.com with ESMTP; 25 Oct 2016 07:32:40 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,545,1473145200"; d="scan'208";a="23813420" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga004.jf.intel.com with ESMTP; 25 Oct 2016 07:32:40 -0700 Received: from bgsmsx154.gar.corp.intel.com (10.224.48.47) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 25 Oct 2016 07:32:40 -0700 Received: from bgsmsx102.gar.corp.intel.com ([169.254.2.202]) by BGSMSX154.gar.corp.intel.com ([169.254.7.140]) with mapi id 14.03.0248.002; Tue, 25 Oct 2016 20:02:36 +0530 From: "Ramia, Kannan Babu" To: Thomas Monjalon CC: "dev@dpdk.org" , Olivier Matz , =?iso-8859-1?Q?Morten_Br=F8rup?= , "Ananyev, Konstantin" , "Richardson, Bruce" , "Wiles, Keith" Thread-Topic: [dpdk-dev] mbuf changes Thread-Index: AdIuDi107p4k5g0aQEmWpCYJ+64TpwAPchyA//8yYwCAAFndAIAAukEAgAATP4CAAAVugIAALESAgABdW+T//6lCgP//koow Date: Tue, 25 Oct 2016 14:32:36 +0000 Message-ID: <682698A055A0F44AA47192B2014114976258DC35@BGSMSX102.gar.corp.intel.com> References: <98CBD80474FA8B44BF855DF32C47DC359EA8B1@smartserver.smartshare.dk> <39b70924-0e66-478c-36ea-dd18d27ed8a6@6wind.com> <5wj6euqlvai26vmpn4dcfe4p.1477400683290@email.android.com> <2277634.HujMj1Cctl@xps13> In-Reply-To: <2277634.HujMj1Cctl@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMjQyNjhlMmQtODI3MC00MDliLWI4ZDItOTg0ZjhjM2RjNzVhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjhqZUJwZm5DR3BqQXl3NUNjRVJWNGprQlwvYTZRbHpxUm9OblFUczUzQzZBPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [10.223.10.10] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] mbuf changes 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: Tue, 25 Oct 2016 14:32:42 -0000 I didn't get your question. The only information exchanged between the stag= es is mbuf pointer. So the information has to be in mbuf, whether it's part= of Meta or in private area in the packet buffer headroom is that the quest= ion you are asking. The private area is application specific, while I am lo= oking for the port information getting updated from driver to application a= nd it's generic to multiple applications.=20 Regards Kannan Babu -----Original Message----- From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]=20 Sent: Tuesday, October 25, 2016 6:54 PM To: Ramia, Kannan Babu Cc: dev@dpdk.org; Olivier Matz ; Morten Br=F8rup ; Ananyev, Konstantin ; Richardson, Bruce ; Wiles, Keith Subject: Re: [dpdk-dev] mbuf changes 2016-10-25 13:04, Ramia, Kannan Babu: > Port filed is important meta information for the application use like=20 > CGNAT vEPC functions etc. > I strongly recommend to keep the field in mind meta. Have you tried to move this field outside of the mbuf? What is the performance degradation? We need more information than some assumptions.