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 613841B4D1 for ; Fri, 1 Feb 2019 15:18:42 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2019 06:18:37 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,549,1539673200"; d="scan'208";a="135066748" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga001.jf.intel.com with ESMTP; 01 Feb 2019 06:18:37 -0800 Received: from fmsmsx108.amr.corp.intel.com ([169.254.9.99]) by fmsmsx104.amr.corp.intel.com ([169.254.3.235]) with mapi id 14.03.0415.000; Fri, 1 Feb 2019 06:18:36 -0800 From: "Eads, Gage" To: Thomas Monjalon , "dev@dpdk.org" CC: "olivier.matz@6wind.com" , "arybchenko@solarflare.com" , "Richardson, Bruce" , "Ananyev, Konstantin" , "stephen@networkplumber.org" , "Mcnamara, John" Thread-Topic: [dpdk-dev] [PATCH v3] doc: announce ring API change Thread-Index: AQHUuh+upRYvFPF4EEGwmZL0XeXt8aXK/Ftw Date: Fri, 1 Feb 2019 14:18:35 +0000 Message-ID: <9184057F7FC11744A2107296B6B8EB1E541CDE4B@FMSMSX108.amr.corp.intel.com> References: <20190118152844.23297-1-gage.eads@intel.com> <20190118153117.23810-1-gage.eads@intel.com> <172114315.O9AQeyJeYo@xps> In-Reply-To: <172114315.O9AQeyJeYo@xps> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjNmMTc3ZWEtZjdhZC00NjdjLWI1ZjAtNWJkNDgzNzk5ZDA2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiUEpxOCtvejlQbEhTYW5KZURma1l2K0xPWGdVRkE2bmp4bEtnSXRUdWVSdCtHc3RCT09pdFFWdTBVcWRYUVRwVyJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.1.200.107] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v3] doc: announce ring API change X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2019 14:18:43 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas@monjalon.net] > Sent: Friday, February 1, 2019 5:17 AM > To: dev@dpdk.org; Eads, Gage > Cc: olivier.matz@6wind.com; arybchenko@solarflare.com; Richardson, Bruce > ; Ananyev, Konstantin > ; stephen@networkplumber.org; Mcnamara, > John > Subject: Re: [dpdk-dev] [PATCH v3] doc: announce ring API change >=20 > 18/01/2019 16:31, Gage Eads: > > In order to support the non-blocking ring[1], an API change > > (additional argument to rte_ring_get_memsize()) is required in > > librte_ring. This commit updates the deprecation notice to pave the > > way for its inclusion in 19.05. > > > > [1] http://mails.dpdk.org/archives/dev/2019-January/123774.html > > > > Signed-off-by: Gage Eads >=20 > Nobody agreed on this change. >=20 > Gage, do you still want to push non-blocking ring in 19.05? >=20 It was optimistic to try for agreement before the 19.02 release :) -- no, l= et's delay it until 19.08. I'll edit and resubmit this patch. >=20 > --- >=20 > > +* ring: one change is planned for rte_ring in v19.05: > > + > > + - rte_ring_get_memsize() will get a new ``flags`` parameter, so it c= an > > + calculate the memory required for rings that require more than 8B = per > entry > > + (such as the upcoming non-blocking ring). >=20 >=20 >=20 >=20