From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 499022BAD for ; Mon, 17 Oct 2016 17:55:12 +0200 (CEST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga104.jf.intel.com with ESMTP; 17 Oct 2016 08:55:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,357,1473145200"; d="scan'208";a="20516612" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga005.jf.intel.com with ESMTP; 17 Oct 2016 08:55:11 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 17 Oct 2016 08:55:10 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.206]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.104]) with mapi id 14.03.0248.002; Mon, 17 Oct 2016 23:55:08 +0800 From: "Chen, Jing D" To: "Zhang, Qi Z" , "Wu, Jingjing" , "Zhang, Helin" CC: "dev@dpdk.org" , "Zhang, Qi Z" Thread-Topic: [dpdk-dev] [PATCH 0/3] net: fix out of order rx read issue Thread-Index: AQHSKIrPkKA5ycSVbkm/WFSNIW7fBqCsy+cQ Date: Mon, 17 Oct 2016 15:55:07 +0000 Message-ID: <4341B239C0EFF9468EE453F9E9F4604D3A39CE44@shsmsx102.ccr.corp.intel.com> References: <1476692614-35793-1-git-send-email-qi.z.zhang@intel.com> In-Reply-To: <1476692614-35793-1-git-send-email-qi.z.zhang@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYmQxOTRjMzYtZDNjYi00N2RiLWFmYmQtNjM2OGZmOGI5YzBhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlViS3hPbTBMYXJJOHhNMzUrQU9ma2drc005eW00RGRCb3BYM3U1eUVKWjQ9In0= x-ctpclassification: CTP_IC x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 0/3] net: fix out of order rx read issue 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: Mon, 17 Oct 2016 15:55:12 -0000 Hi, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qi Zhang > Sent: Monday, October 17, 2016 1:24 AM > To: Wu, Jingjing ; Zhang, Helin > > Cc: dev@dpdk.org; Zhang, Qi Z > Subject: [dpdk-dev] [PATCH 0/3] net: fix out of order rx read issue >=20 > Volatile point has been cast to non-volatile point when call _mm_loadu_si= 128, > so add compile barrier to prevent compiler reorder. >=20 > Qi Zhang (3): > net/i40e: fix out of order rx read issue > net/ixgbe: fix out of order rx read issue > net/fm10k: fix out of order rx read issue >=20 > drivers/net/fm10k/fm10k_rxtx_vec.c | 3 +++ > drivers/net/i40e/i40e_rxtx_vec.c | 3 +++ > drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c | 3 +++ > 3 files changed, 9 insertions(+) I have an overall comment on the committed message. You'd better to describ= e why we have out of order issue here and the requirement on the execution or= der of the 4 loads.=20