From: Rusty Russell <rusty@rustcorp.com.au>
To: Robert Love <rml@tech9.net>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] per-cpu patch 2/3
Date: Fri, 19 Jul 2002 11:36:20 +1000 [thread overview]
Message-ID: <20020719014425.9F57E4109@lists.samba.org> (raw)
In-Reply-To: Your message of "18 Jul 2002 10:05:26 MST." <1027011926.1086.118.camel@sinai>
In message <1027011926.1086.118.camel@sinai> you write:
> On Wed, 2002-07-17 at 20:48, Rusty Russell wrote:
> > Given the ongoing races with smp_processor_id() and preempt, this
> > makes sense to me. this_cpu() was too generic a name anyway.
>
> Very nice, although:
>
> How do you reenable preemption?
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?
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-07-19 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 3:48 [PATCH] per-cpu patch 2/3 Rusty Russell
2002-07-18 17:05 ` Robert Love
2002-07-19 1:36 ` Rusty Russell [this message]
2002-07-19 17:49 ` Robert Love
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=20020719014425.9F57E4109@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--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 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.