Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754792AbbDJIW4 (ORCPT ); Fri, 10 Apr 2015 04:22:56 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:37089 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753964AbbDJIWu (ORCPT ); Fri, 10 Apr 2015 04:22:50 -0400 Date: Fri, 10 Apr 2015 10:22:45 +0200 From: Ingo Molnar To: Peter Zijlstra Cc: Kirill Tkhai , linux-kernel@vger.kernel.org, Oleg Nesterov , Andrew Morton , Ingo Molnar , Michal Hocko , Rik van Riel , Ionut Alexa , Peter Hurley , Kirill Tkhai , Linus Torvalds Subject: Re: [PATCH] exit: Use read lock for do_notify_parent() instead of write lock Message-ID: <20150410082245.GA25842@gmail.com> References: <1428602348.12166.29.camel@parallels.com> <20150409182838.GZ5029@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150409182838.GZ5029@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 976 Lines: 30 * Peter Zijlstra wrote: > On Thu, Apr 09, 2015 at 08:59:08PM +0300, Kirill Tkhai wrote: > > I've not really read your email yet, however: > > > Also, in the future we may think about new rwlock primitive, which atomically > > drops write lock and acquires read lock. Something like this for example: > > > > include/asm-generic/qrwlock.h: > > static inline void queue_reduce_locked_write_to_read(struct qrwlock *lock) > > { > > smp_mb__before_atomic(); > > atomic_add(_QR_BIAS - _QW_LOCKED, &lock->cnts); > > } > > we actually have that for the rwsems: downgrade_write(). So the > consistent naming would be: queue_downgrade_write(). and 'downgrade_write_lock()' on the rwlock side. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/