All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: cl@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	David Howells <dhowells@redhat.com>, Ingo Molnar <mingo@elte.hu>,
	Eric Dumazet <dada1@cosmosbay.com>,
	davem@davemloft.net
Subject: Re: [my_cpu_ptr 1/5] Introduce my_cpu_ptr()
Date: Thu, 28 May 2009 13:16:01 +0930	[thread overview]
Message-ID: <200905281316.01923.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090527180714.834691580@gentwo.org>

On Thu, 28 May 2009 03:16:59 am cl@linux-foundation.org wrote:
> my_cpu_ptr(xx) = per_cpu_ptr(xx, smp_processor_id).

I had this implemented earlier as as get_cpu_ptr()/__get_cpu_ptr(), to match 
get_cpu_var() / __get_cpu_var().

But other than that nomenclature quibble, it looks fine!

Thanks,
Rusty.

  reply	other threads:[~2009-05-28  3:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 17:46 [my_cpu_ptr 0/5] Introduce my_cpu_ptr/__my_cpu_ptr cl
2009-05-27 17:46 ` [my_cpu_ptr 1/5] Introduce my_cpu_ptr() cl
2009-05-28  3:46   ` Rusty Russell [this message]
2009-05-28 15:59     ` Christoph Lameter
2009-05-29  1:27       ` Rusty Russell
2009-05-29 15:37         ` Christoph Lameter
2009-05-31  3:19           ` Rusty Russell
2009-06-03 14:08             ` Christoph Lameter
2009-05-28 16:10     ` Christoph Hellwig
2009-05-28 16:37       ` Christoph Lameter
2009-05-29  9:46         ` Tejun Heo
2009-05-27 17:47 ` [my_cpu_ptr 2/5] Straight transformations cl
2009-05-27 17:47 ` [my_cpu_ptr 3/5] Elimninate get/put_cpu cl
2009-05-27 19:33   ` Christoph Lameter
2009-05-27 17:47 ` [my_cpu_ptr 4/5] sda_icsb_modify_counters() does not need a "cpu" variable cl
2009-05-28 13:45   ` Olaf Weber
2009-05-27 17:47 ` [my_cpu_ptr 5/5] Use my_cpu_ptr in crypto subsystem cl

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=200905281316.01923.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=cl@linux-foundation.org \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.