From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerin Jacob Subject: Re: [PATCH v3 1/3] ring: read tail using atomic load Date: Mon, 8 Oct 2018 17:50:39 +0530 Message-ID: <20181008122038.GD28968@jerin> References: <7A156041-23EC-4CCB-B129-3607AF34A992@arm.com> <20181008060629.GA5228@jerin> <063A95EC-CFC1-42F7-B864-DFB9C6718AC8@arm.com> <20181008100004.GB11081@jerin> <20181008104653.GC11081@jerin> <20181008115028.GA28968@jerin> <22595D8F-00A6-4D45-B143-2BF25148869D@arm.com> <20181008120524.GC28968@jerin> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: "dev@dpdk.org" , Honnappa Nagarahalli , "Ananyev, Konstantin" , "Gavin Hu (Arm Technology China)" , Steve Capper , nd , "stable@dpdk.org" To: Ola Liljedahl Return-path: Content-Disposition: inline In-Reply-To: <20181008120524.GC28968@jerin> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" -----Original Message----- > Date: Mon, 8 Oct 2018 17:35:25 +0530 > From: Jerin Jacob > To: Ola Liljedahl > CC: "dev@dpdk.org" , Honnappa Nagarahalli > , "Ananyev, Konstantin" > , "Gavin Hu (Arm Technology China)" > , Steve Capper , nd , > "stable@dpdk.org" > Subject: Re: [dpdk-dev] [PATCH v3 1/3] ring: read tail using atomic load > User-Agent: Mutt/1.10.1 (2018-07-13) > > External Email > > -----Original Message----- > > Date: Mon, 8 Oct 2018 11:59:16 +0000 > > From: Ola Liljedahl > > To: Jerin Jacob > > CC: "dev@dpdk.org" , Honnappa Nagarahalli > > , "Ananyev, Konstantin" > > , "Gavin Hu (Arm Technology China)" > > , Steve Capper , nd , > > "stable@dpdk.org" > > Subject: Re: [PATCH v3 1/3] ring: read tail using atomic load > > user-agent: Microsoft-MacOutlook/10.11.0.180909 > > > > > > On 08/10/2018, 13:50, "Jerin Jacob" wrote: > > > > > > I don't know how that creates more undefined behavior. So replied in the > > context of your reply that, according to your view even Linux is running > > with undefined behavior. > > > > As I explained, Linux does not use C11 atomics (nor GCC __atomic builtins) so > > cannot express the kind of undefined behaviour caused by mixing conflicting atomic > > (as defined by the C11 standard) and non-atomic accesses to the same object. > > > > Checked the latest version from https://github.com/torvalds/linux > > Yet another top post. So you removed the complete earlier context. Never > mind. > > I am not saying Linux is using C11 atomic. I asked, Can't we follow > like Linux to use the HW feature of load acquire and store release > semantics with introducing C11 memory model. correction: s/with introducing C11 memory model/with out introducing C11 memory model > > > > > > >