From: Rusty Russell <rusty@rustcorp.com.au>
To: Jamie Lokier <jamie@shareable.org>
Cc: torvalds@transmeta.com, akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] percpu struct members.
Date: Tue, 22 Jul 2003 07:27:41 +1000 [thread overview]
Message-ID: <20030721213554.723822C0FD@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 21 Jul 2003 19:56:19 +0100." <20030721185619.GB6912@mail.jlokier.co.uk>
In message <20030721185619.GB6912@mail.jlokier.co.uk> you write:
> Rusty Russell wrote:
> > The current percpu macros do not allow __get_cpu_var(foo.val1)
> > which makes building macros on top of them really difficult.
>
> What's the problem with __get_cpu_var(foo).val1 ?
Nothing: that will still work, too. But not say you have a macro (as
we do in local_t):
local_cpu_inc(cpuvar)
if cpuvar is a struct, you want this to work:
local_cpu_inc(cpuvar.member)
Hope that helps,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2003-07-21 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 8:35 [PATCH 2/5] percpu struct members Rusty Russell
2003-07-21 18:56 ` Jamie Lokier
2003-07-21 21:27 ` Rusty Russell [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=20030721213554.723822C0FD@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).