From: David Gibson <david@gibson.dropbear.id.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] __cacheline_aligned_in_smp?
Date: Mon, 13 Jan 2003 20:41:12 +1100 [thread overview]
Message-ID: <20030113094112.GA498@zax.zax> (raw)
In-Reply-To: <20030113072521.74B842C104@lists.samba.org>
On Mon, Jan 13, 2003 at 06:24:40PM +1100, Paul 'Rusty' Russell wrote:
> Dave: Anton suggested you might have a justification for
> __cacheline_aligned doing something on UP?
It could matter for DMA buffers on UP machines with non-cache coherent
DMA.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
prev parent reply other threads:[~2003-01-13 9:36 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
2003-01-13 9:41 ` David Gibson [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=20030113094112.GA498@zax.zax \
--to=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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