linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: Tejun Heo <tj@kernel.org>
Cc: akpm@linuxfoundation.org, linux-arch@vger.kernel.org,
	Steven Rostedt <srostedt@redhat.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH 08/10] percpu: Replace __get_cpu_var uses
Date: Tue, 15 Oct 2013 12:59:00 -0500	[thread overview]
Message-ID: <20131015180053.750416164@linux.com> (raw)
In-Reply-To: 20131015175852.122827685@linux.com

[-- Attachment #1: this_percpu --]
[-- Type: text/plain, Size: 3026 bytes --]

__get_cpu_var() is used for multiple purposes in the kernel source. One of them is
address calculation via the form &__get_cpu_var(x). This calculates the address for
the instance of the percpu variable of the current processor based on an offset.

Other use cases are for storing and retrieving data from the current processors percpu area.
__get_cpu_var() can be used as an lvalue when writing data or on the right side of an assignment.

__get_cpu_var() is defined as :


#define __get_cpu_var(var) (*this_cpu_ptr(&(var)))



__get_cpu_var() always only does an address determination. However, store
and retrieve operations could use a segment prefix (or global register on
other platforms) to avoid the address calculation.

this_cpu_write() and this_cpu_read() can directly take an offset into a
percpu area and use optimized assembly code to read and write per cpu
variables.


This patch converts __get_cpu_var into either an explicit address
calculation using this_cpu_ptr() or into a use of this_cpu operations that
use the offset.  Thereby address calculations are avoided and less registers
are used when code is generated.

At the end of the patch set all uses of __get_cpu_var have been removed so
the macro is removed too.

The patch set includes passes over all arches as well. Once these operations
are used throughout then specialized macros can be defined in non -x86
arches as well in order to optimize per cpu access by f.e.  using a global
register that may be set to the per cpu base.




Transformations done to __get_cpu_var()


1. Determine the address of the percpu instance of the current processor.

	DEFINE_PER_CPU(int, y);
	int *x = &__get_cpu_var(y);

    Converts to

	int *x = this_cpu_ptr(&y);


2. Same as #1 but this time an array structure is involved.

	DEFINE_PER_CPU(int, y[20]);
	int *x = __get_cpu_var(y);

    Converts to

	int *x = this_cpu_ptr(y);


3. Retrieve the content of the current processors instance of a per cpu
variable.

	DEFINE_PER_CPU(int, y);
	int x = __get_cpu_var(y)

   Converts to

	int x = __this_cpu_read(y);


4. Retrieve the content of a percpu struct

	DEFINE_PER_CPU(struct mystruct, y);
	struct mystruct x = __get_cpu_var(y);

   Converts to

	memcpy(&x, this_cpu_ptr(&y), sizeof(x));


5. Assignment to a per cpu variable

	DEFINE_PER_CPU(int, y)
	__get_cpu_var(y) = x;

   Converts to

	this_cpu_write(y, x);


6. Increment/Decrement etc of a per cpu variable

	DEFINE_PER_CPU(int, y);
	__get_cpu_var(y)++

   Converts to

	this_cpu_inc(y)

Signed-off-by: Christoph Lameter <cl@linux.com>

Index: linux/include/linux/percpu.h
===================================================================
--- linux.orig/include/linux/percpu.h	2013-08-26 14:29:49.000000000 -0500
+++ linux/include/linux/percpu.h	2013-08-26 14:30:18.302570608 -0500
@@ -28,7 +28,7 @@
  */
 #define get_cpu_var(var) (*({				\
 	preempt_disable();				\
-	&__get_cpu_var(var); }))
+	this_cpu_ptr(&var); }))
 
 /*
  * The weird & is necessary because sparse considers (void)(var) to be

  parent reply	other threads:[~2013-10-15 17:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 17:58 [PATCH 00/10] percpu: Replace __get_cpu_var uses in core code V1 Christoph Lameter
2013-10-15 17:58 ` Christoph Lameter
2013-10-15 17:58 ` [PATCH 01/10] net: Replace __get_cpu_var uses Christoph Lameter
2013-10-15 17:58   ` Christoph Lameter
2013-10-15 17:58 ` [PATCH 02/10] time: " Christoph Lameter
2013-10-15 17:58   ` Christoph Lameter
2013-10-15 17:58 ` [PATCH 03/10] scheduler: " Christoph Lameter
2013-10-15 17:58   ` Christoph Lameter
2013-10-15 17:58 ` [PATCH 04/10] mm: " Christoph Lameter
2013-10-15 17:58   ` Christoph Lameter
2013-10-15 17:58 ` [PATCH 05/10] tracing: " Christoph Lameter
2013-10-15 17:58   ` Christoph Lameter
2013-10-15 17:58 ` [PATCH 06/10] block: " Christoph Lameter
2013-10-15 17:58   ` Christoph Lameter
2013-10-15 18:22   ` Jens Axboe
2013-10-15 17:58 ` [PATCH 07/10] rcu: " Christoph Lameter
2013-10-15 17:58   ` Christoph Lameter
2013-10-15 19:25   ` Paul E. McKenney
2013-10-15 19:25     ` Paul E. McKenney
2013-10-15 17:59 ` Christoph Lameter [this message]
2013-10-15 17:59   ` [PATCH 08/10] percpu: " Christoph Lameter
2013-10-15 17:59 ` [PATCH 09/10] watchdog: " Christoph Lameter
2013-10-15 17:59   ` Christoph Lameter
2013-10-15 17:59 ` [PATCH 10/10] kernel misc: " Christoph Lameter
2013-10-15 17:59   ` Christoph Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131015180053.750416164@linux.com \
    --to=cl@linux.com \
    --cc=akpm@linuxfoundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=srostedt@redhat.com \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).