From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751188AbbJaTGn (ORCPT ); Sat, 31 Oct 2015 15:06:43 -0400 Received: from mx2.suse.de ([195.135.220.15]:58565 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750864AbbJaTGm (ORCPT ); Sat, 31 Oct 2015 15:06:42 -0400 Date: Sat, 31 Oct 2015 12:06:33 -0700 From: Davidlohr Bueso To: George Spelvin Cc: bigeasy@linutronix.de, tglx@linutronix.de, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, manfred@colorfullife.com, peterz@infradead.org Subject: Re: [PATCH] ipc/msg: Implement lockless pipelined wakeups Message-ID: <20151031190633.GA1707@linux-uzut.site> References: <20151031130214.10598.qmail@ns.horizon.com> <20151031185457.GC7947@linux-uzut.site> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20151031185457.GC7947@linux-uzut.site> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 31 Oct 2015, Bueso wrote: >Yes, and this confirms that we still rely on the implicit barrier >from the cmpxchg as tglx mentioned. As such, we also need to keep >the pairing when reading 'r_msg' in do_msgrcv(), instead of dropping >the comments. Hmm having r_msg as volatile seems even less needed now, we should drop it. I imagine it was there initially for the busy-wait on the variable becoming non-nil, but we had cpu_relax _anyway_, so ...