From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752176AbbE0Gxz (ORCPT ); Wed, 27 May 2015 02:53:55 -0400 Received: from casper.infradead.org ([85.118.1.10]:48750 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751236AbbE0Gxy (ORCPT ); Wed, 27 May 2015 02:53:54 -0400 Date: Wed, 27 May 2015 08:53:49 +0200 From: Peter Zijlstra To: Davidlohr Bueso Cc: Linus Torvalds , Oleg Nesterov , Paul McKenney , Tejun Heo , Ingo Molnar , Linux Kernel Mailing List , der.herr@hofr.at Subject: Re: [RFC][PATCH 0/5] Optimize percpu-rwsem Message-ID: <20150527065349.GS3644@twins.programming.kicks-ass.net> References: <20150526114356.609107918@infradead.org> <1432665731.8196.3.camel@stgolabs.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1432665731.8196.3.camel@stgolabs.net> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 26, 2015 at 11:42:11AM -0700, Davidlohr Bueso wrote: > Instead of dropping percpu-rwsem, I was thinking we could instead look > for opportunities to convert new users, for instance shinkers, where the > write lock is also taken just for register and unregister purposes, > similar to uprobes. Another 'obvious' one would be the cpu hotplug lock. That's basically the same locking primitive with just a wee little difference.