From patchwork Mon Feb 18 12:39:07 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Srivatsa S. Bhat" X-Patchwork-Id: 2158521 Return-Path: X-Original-To: patchwork-linux-pm@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork1.kernel.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by patchwork1.kernel.org (Postfix) with ESMTP id 8F8343FDF1 for ; Mon, 18 Feb 2013 12:56:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754386Ab3BRMlV (ORCPT ); Mon, 18 Feb 2013 07:41:21 -0500 Received: from e28smtp01.in.ibm.com ([122.248.162.1]:35917 "EHLO e28smtp01.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754331Ab3BRMlR (ORCPT ); Mon, 18 Feb 2013 07:41:17 -0500 Received: from /spool/local by e28smtp01.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 18 Feb 2013 18:08:33 +0530 Received: from d28dlp01.in.ibm.com (9.184.220.126) by e28smtp01.in.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 18 Feb 2013 18:08:29 +0530 Received: from d28relay04.in.ibm.com (d28relay04.in.ibm.com [9.184.220.61]) by d28dlp01.in.ibm.com (Postfix) with ESMTP id 8137FE0050; Mon, 18 Feb 2013 18:12:07 +0530 (IST) Received: from d28av04.in.ibm.com (d28av04.in.ibm.com [9.184.220.66]) by d28relay04.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r1ICf87X25624798; Mon, 18 Feb 2013 18:11:08 +0530 Received: from d28av04.in.ibm.com (loopback [127.0.0.1]) by d28av04.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r1ICf5F0018691; Mon, 18 Feb 2013 23:41:09 +1100 Received: from srivatsabhat.in.ibm.com (srivatsabhat.in.ibm.com [9.124.35.204] (may be forged)) by d28av04.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r1ICf4Dw018633; Mon, 18 Feb 2013 23:41:04 +1100 From: "Srivatsa S. Bhat" Subject: [PATCH v6 06/46] percpu_rwlock: Rearrange the read-lock code to fastpath nested percpu readers To: tglx@linutronix.de, peterz@infradead.org, tj@kernel.org, oleg@redhat.com, paulmck@linux.vnet.ibm.com, rusty@rustcorp.com.au, mingo@kernel.org, akpm@linux-foundation.org, namhyung@kernel.org Cc: rostedt@goodmis.org, wangyun@linux.vnet.ibm.com, xiaoguangrong@linux.vnet.ibm.com, rjw@sisk.pl, sbw@mit.edu, fweisbec@gmail.com, linux@arm.linux.org.uk, nikunj@linux.vnet.ibm.com, srivatsa.bhat@linux.vnet.ibm.com, linux-pm@vger.kernel.org, linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, netdev@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, walken@google.com, vincent.guittot@linaro.org Date: Mon, 18 Feb 2013 18:09:07 +0530 Message-ID: <20130218123907.26245.37550.stgit@srivatsabhat.in.ibm.com> In-Reply-To: <20130218123714.26245.61816.stgit@srivatsabhat.in.ibm.com> References: <20130218123714.26245.61816.stgit@srivatsabhat.in.ibm.com> User-Agent: StGIT/0.14.3 MIME-Version: 1.0 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13021812-4790-0000-0000-000006F5F0CC Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org If we are dealing with a nester percpu reader, we can optimize away quite a few costly operations. Improve that fastpath further, by avoiding the unnecessary addition and subtraction of 'READER_PRESENT' to reader_refcnt, by rearranging the code a bit. Signed-off-by: Srivatsa S. Bhat --- lib/percpu-rwlock.c | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/lib/percpu-rwlock.c b/lib/percpu-rwlock.c index ce7e440..ed36531 100644 --- a/lib/percpu-rwlock.c +++ b/lib/percpu-rwlock.c @@ -80,23 +80,21 @@ void percpu_read_lock_irqsafe(struct percpu_rwlock *pcpu_rwlock) preempt_disable(); /* - * Let the writer know that a reader is active, even before we choose - * our reader-side synchronization scheme. - */ - this_cpu_add(pcpu_rwlock->rw_state->reader_refcnt, READER_PRESENT); - - /* * If we are already using per-cpu refcounts, it is not safe to switch * the synchronization scheme. So continue using the refcounts. */ if (reader_uses_percpu_refcnt(pcpu_rwlock)) { this_cpu_inc(pcpu_rwlock->rw_state->reader_refcnt); - this_cpu_sub(pcpu_rwlock->rw_state->reader_refcnt, - READER_PRESENT); return; } /* + * Let the writer know that a reader is active, even before we choose + * our reader-side synchronization scheme. + */ + this_cpu_add(pcpu_rwlock->rw_state->reader_refcnt, READER_PRESENT); + + /* * The write to 'reader_refcnt' must be visible before we read * 'writer_signal'. */