From: Rusty Russell <rusty@rustcorp.com.au>
To: "David S. Miller" <davem@redhat.com>
Cc: akpm@zip.com.au, torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] __cacheline_aligned_in_smp?
Date: Tue, 14 Jan 2003 12:10:12 +1100 [thread overview]
Message-ID: <20030114121012.63554a44.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20030112.233513.83403887.davem@redhat.com>
On Sun, 12 Jan 2003 23:35:13 -0800 (PST)
"David S. Miller" <davem@redhat.com> wrote:
> All of the submembers are placed at cacheline boundaries, which
> helps even on UP. If I meant cacheline aligned on SMP I would
> have used the corresponding macro :)
Hmm, you really want to weakly align it: you don't care if something follows it on
the cacheline, (ie. don't make it into an array, but it'd be nice if other
things could share the cacheline) in UP.
I don't think there's a way of doing that short of using asm?
It'd be nice if someone volunteered benchmarks. struct tcp_hashinfo takes
*two* whole cachlines, for example:
> -struct tcp_hashinfo __cacheline_aligned tcp_hashinfo = {
> +struct tcp_hashinfo __cacheline_aligned_in_smp tcp_hashinfo = {
>
> This definitely too.
The decl already puts the non-read-heavy members __cacheline_aligned:
extern struct tcp_hashinfo {
...
rwlock_t __tcp_lhash_lock ____cacheline_aligned;
*This* should probably be ____cacheline_aligned_in_smp, yes?
Thanks for the reply!
Rusty.
--
there are those who do and those who hang on and you don't see too
many doers quoting their contemporaries. -- Larry McVoy
next prev parent reply other threads:[~2003-01-14 2:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 7:24 [PATCH] __cacheline_aligned_in_smp? Rusty Russell
2003-01-13 7:35 ` David S. Miller
2003-01-14 1:10 ` Rusty Russell [this message]
2003-01-14 6:32 ` David S. Miller
2003-01-15 8:02 ` Rusty Russell
2003-01-16 7:21 ` David S. Miller
2003-01-21 14:09 ` Bill Davidsen
2003-01-13 7:45 ` Jeff Garzik
2003-01-14 2:22 ` Rusty Russell
2003-01-13 9:41 ` David Gibson
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=20030114121012.63554a44.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=davem@redhat.com \
--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