From: James Bottomley <James.Bottomley@steeleye.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFT][PATCH] generic device DMA implementation
Date: Sat, 28 Dec 2002 12:13:23 -0600 [thread overview]
Message-ID: <200212281813.gBSIDNP02885@localhost.localdomain> (raw)
In-Reply-To: Message from Manfred Spraul <manfred@colorfullife.com> of "Sat, 28 Dec 2002 18:54:49 +0100." <3E0DE569.9070108@colorfullife.com>
manfred@colorfullife.com said:
> You are aware that "users" is not one or two drivers that noone uses,
> it's the whole networking stack.
I am aware of this. I'm also aware that it is *currently* broken with the old
API on all non-coherent arch's bar the one you point out.
All I actually did was document the existing problem, I think.
How bad actually is it? Networking seems to work fine for me on non-coherent
parisc. Whereas, when I had this cache line overlap problem in a SCSI driver,
I was seeing corruption all over the place.
The problem really only occurs if the CPU can modify part of a cache line
while a device has modified memory belonging to another part. Now a flush
from the CPU will destroy the device data (or an invalidate from the driver
destroy the CPU's data). The problem is effectively rendered harmless if only
data going in the same direction shares a cache line (even if it is for
different devices). It strikes me that this is probably true for network data
and would explain the fact that I haven't seen any obvious network related
corruption.
James
next prev parent reply other threads:[~2002-12-28 18:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 22:57 [RFT][PATCH] generic device DMA implementation Manfred Spraul
2002-12-27 23:55 ` James Bottomley
2002-12-28 0:20 ` Manfred Spraul
2002-12-28 16:26 ` James Bottomley
2002-12-28 17:54 ` Manfred Spraul
2002-12-28 18:13 ` James Bottomley [this message]
2002-12-28 18:25 ` Manfred Spraul
2002-12-28 18:40 ` James Bottomley
2002-12-28 20:05 ` Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2002-12-28 22:19 Adam J. Richter
2002-12-30 23:23 ` David Brownell
2002-12-28 20:11 Adam J. Richter
2002-12-28 15:41 Adam J. Richter
2002-12-28 16:59 ` David Brownell
2002-12-28 3:39 Adam J. Richter
2002-12-30 0:45 ` Alan Cox
2002-12-28 2:48 Adam J. Richter
2002-12-28 15:05 ` David Brownell
2002-12-27 20:21 David Brownell
2002-12-27 21:40 ` James Bottomley
2002-12-28 1:29 ` David Brownell
2002-12-28 16:18 ` James Bottomley
2002-12-28 18:16 ` David Brownell
2002-12-28 1:56 ` David Brownell
2002-12-28 16:13 ` James Bottomley
2002-12-28 17:41 ` David Brownell
2002-12-27 21:47 ` James Bottomley
2002-12-28 2:28 ` David Brownell
2002-12-18 3:01 James Bottomley
2002-12-18 3:13 ` David Mosberger
2002-12-28 18:14 ` Russell King
2002-12-28 18:19 ` James Bottomley
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=200212281813.gBSIDNP02885@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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