From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx3-rdu2.redhat.com ([66.187.233.73]:49148 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752634AbeEOMph (ORCPT ); Tue, 15 May 2018 08:45:37 -0400 Date: Tue, 15 May 2018 14:45:32 +0200 From: Oleg Nesterov To: Peter Zijlstra Cc: Waiman Long , Ingo Molnar , Thomas Gleixner , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Davidlohr Bueso , "Theodore Y. Ts'o" , Amir Goldstein , Jan Kara Subject: Re: [RFC PATCH v2 2/2] locking/percpu-rwsem: Mark rwsem as non-spinnable in percpu_rwsem_release() Message-ID: <20180515124532.GA19429@redhat.com> References: <1526326267-22501-1-git-send-email-longman@redhat.com> <1526326267-22501-3-git-send-email-longman@redhat.com> <20180515085111.GW12217@hirez.programming.kicks-ass.net> <20180515110632.GA14527@redhat.com> <20180515115112.GZ12217@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180515115112.GZ12217@hirez.programming.kicks-ass.net> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 05/15, Peter Zijlstra wrote: > > > > Afaict the whole .owner=NULL thing in release already stops the spinners > > > > Not really, the new writer will spin in this case, afaics. > > > > But this is another problem and probably we do not care. The new writer is > > almost impossible in this particular case, another freeze_super() should > > notice frozen != SB_UNFROZEN and return EBUSY. > > rwsem_spin_on_owner() checks rwsem_owner_is_writer(), which does owner > && owner != RWSEM_READER_OWNED, which will fail for !owner. Yep. So rwsem_spin_on_owner() goes to "out:" and returns !rwsem_owner_is_reader() == T. IOW, afaics owner == NULL means "spin unconditionally", I guess this is for the case when the new writer is going to do rwsem_set_owner() or up_write() has already called rwsem_clear_owner() but didn't do up_write() yet. Probably makes sense, but the code is not very clean, > Or am I completely confused again? Or me, I am not sure. Oleg.