From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: akpm@zip.com.au, davem@redhat.com, torvalds@transmeta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] __cacheline_aligned_in_smp?
Date: Tue, 14 Jan 2003 13:22:46 +1100 [thread overview]
Message-ID: <20030114025452.896E52C3DD@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 13 Jan 2003 02:45:16 CDT." <20030113074516.GA4677@gtf.org>
In message <20030113074516.GA4677@gtf.org> you write:
> On Mon, Jan 13, 2003 at 06:24:40PM +1100, Rusty Russell wrote:
> > Dave: Anton suggested you might have a justification for
> > __cacheline_aligned doing something on UP?
> >
> > I think I'd prefer __cacheline_aligned to be the same as
> > __cacheline_aligned_in_smp, and have a new __cacheline_aligned_always
> > for those who REALLY want it (if any).
>
> See the recent thread on tg3 and cacheline_aligned for David's
> description... I and one other did some performance measurements and
> ____cacheline_aligned proved useful even on UP...
Thanks, finally found the thread.
> sigh. I wish I had caught you on IRC.
<sniff> I miss you too Jeff... 8)
> Don't you think changing the meaning of cacheline_aligned, and adding a
> new __cacheline_aligned_always to mean what it used to, is completely
> pointless churn??
Agreed. Now I understand that's it's also possibly useful on UP, not
just programmer laziness, like it is in the module.h case 8)
Of course, it'd be nice to see benchmarks to justify each of these,
but wouldn't it always?
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
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
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 [this message]
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=20030114025452.896E52C3DD@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.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