From: Robert Love <rml@tech9.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] per-cpu patch 2/3
Date: 19 Jul 2002 10:49:28 -0700 [thread overview]
Message-ID: <1027100968.1116.194.camel@sinai> (raw)
In-Reply-To: <20020719014425.9F57E4109@lists.samba.org>
On Thu, 2002-07-18 at 18:36, Rusty Russell wrote:
> I think you are confused: this patch is an enhancement of the per-cpu
> variable infrastructure. I was making an analogy with
> smp_processor_id().
>
> +#define get_cpu_var(var) ({ preempt_disable(); __get_cpu_var(var); })
> +#define put_cpu_var(var) preempt_enable()
>
> Clear?
as day.
sorry,
Robert Love
prev parent reply other threads:[~2002-07-19 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 3:48 Rusty Russell
2002-07-18 17:05 ` Robert Love
2002-07-19 1:36 ` Rusty Russell
2002-07-19 17:49 ` Robert Love [this message]
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=1027100968.1116.194.camel@sinai \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®