From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id CB8FE1B94B for ; Fri, 11 Jan 2019 03:51:18 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jan 2019 18:51:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,463,1539673200"; d="scan'208";a="137284504" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga001.fm.intel.com with ESMTP; 10 Jan 2019 18:51:17 -0800 Received: from fmsmsx126.amr.corp.intel.com (10.18.125.43) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 10 Jan 2019 18:51:17 -0800 Received: from bgsmsx155.gar.corp.intel.com (10.224.48.102) by FMSMSX126.amr.corp.intel.com (10.18.125.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 10 Jan 2019 18:51:16 -0800 Received: from bgsmsx101.gar.corp.intel.com ([169.254.1.128]) by BGSMSX155.gar.corp.intel.com ([169.254.12.54]) with mapi id 14.03.0415.000; Fri, 11 Jan 2019 08:21:13 +0530 From: "Varghese, Vipin" To: "Eads, Gage" , "dev@dpdk.org" CC: "olivier.matz@6wind.com" , "arybchenko@solarflare.com" , "Richardson, Bruce" , "Ananyev, Konstantin" Thread-Topic: [dpdk-dev] [PATCH 6/6] doc: add NB ring comment to EAL "known issues" Thread-Index: AQHUqSf8gXt/PS+CPkCPfdH1XFZKyaWpXnOQ Date: Fri, 11 Jan 2019 02:51:12 +0000 Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2EFBC2@BGSMSX101.gar.corp.intel.com> References: <20190110210122.24889-1-gage.eads@intel.com> <20190110210122.24889-7-gage.eads@intel.com> In-Reply-To: <20190110210122.24889-7-gage.eads@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZGRlNjZhNmQtNmM5Zi00YTYxLWE4ZTUtODJhZTEwNWEwNzg2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiaFRHcFN2RnRFc3Z5Smt4UEhUMk9wSU42UkZMb09KdldicjZIMk1mb21meVkyXC8zcEVBS1YzaHcxeERVcE90ZE4ifQ== dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.223.10.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 6/6] doc: add NB ring comment to EAL "known issues" 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, 11 Jan 2019 02:51:19 -0000 Hi Gage, Humble suggestion from my end, as per DPDK 19.02-rc1 the documentation and = code change have to be in same patch. Can you please take a look into it. > -----Original Message----- > From: dev On Behalf Of Gage Eads > Sent: Friday, January 11, 2019 2:31 AM > To: dev@dpdk.org > Cc: olivier.matz@6wind.com; arybchenko@solarflare.com; Richardson, Bruce > ; Ananyev, Konstantin > > Subject: [dpdk-dev] [PATCH 6/6] doc: add NB ring comment to EAL "known > issues" >=20 > This comment makes users aware of the non-blocking ring option and its > caveats. >=20 > Signed-off-by: Gage Eads > --- > doc/guides/prog_guide/env_abstraction_layer.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >=20 > diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst > b/doc/guides/prog_guide/env_abstraction_layer.rst > index 9497b879c..b6ac236d6 100644 > --- a/doc/guides/prog_guide/env_abstraction_layer.rst > +++ b/doc/guides/prog_guide/env_abstraction_layer.rst > @@ -541,7 +541,7 @@ Known Issues >=20 > 5. It MUST not be used by multi-producer/consumer pthreads, whose > scheduling policies are SCHED_FIFO or SCHED_RR. >=20 > - Alternatively, x86_64 applications can use the non-blocking stack memp= ool > handler. When considering this handler, note that: > + Alternatively, x86_64 applications can use the non-blocking ring or st= ack > mempool handlers. When considering one of them, note that: >=20 > - it is limited to the x86_64 platform, because it uses an instruction= (16-byte > compare-and-swap) that is not available on other platforms. > - it has worse average-case performance than the non-preemptive rte_ri= ng, > but software caching (e.g. the mempool cache) can mitigate this by reduci= ng > the number of handler operations. > -- > 2.13.6