From: Deepak Saxena <dsaxena@plexity.net>
To: "David S. Miller" <davem@redhat.com>
Cc: mporter@kernel.crashing.org, lists@mdiehl.de,
linux-kernel@vger.kernel.org
Subject: Re: [Patch] dma_sync_to_device
Date: Wed, 11 Feb 2004 20:46:11 -0700 [thread overview]
Message-ID: <20040212034610.GA27317@plexity.net> (raw)
In-Reply-To: <20040211110853.492f479b.davem@redhat.com>
On Feb 11 2004, at 11:08, David S. Miller was caught saying:
> New sequence:
>
> 1) pci_map_single(..., DMA_TO_DEVICE). Flush dirty data from cpu caches to memory,
> so device may see it.
>
> 2) device reads buffer
>
> 3) pci_dma_sync_single(... DMA_TO_DEVICE). If PCI controller has caches, flush them.
>
> 4) CPU writes new buffer data.
>
> 5) pci_dma_sync_device_single(... DMA_TO_DEVICE). Like #1, flush dirty data from cpu
> caches to memory.
>
> 6) Device reads buffer.
>
> Still disagree? :-)
/me groks now. I am assuming this is a 2.7 thing as it is
reinterpreting/redefining the API. In ARM, pci_dma_sync_single() does
a cache flush, which is why I was confused asked about two cache flushes.
What you are proposing is that by definition pci_dma_sync_* syncs
bridges caches with system memory, while pci_dma_sync_device_* syncs
the CPU's cache with system memory.
This will definetely confuse a lot of driver writers.
~Deepak
--
Deepak Saxena - dsaxena at plexity dot net - http://www.plexity.net/
next prev parent reply other threads:[~2004-02-12 3:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 17:31 [Patch] dma_sync_to_device Martin Diehl
2004-02-10 18:42 ` David S. Miller
2004-02-10 18:59 ` Martin Diehl
2004-02-11 6:17 ` Deepak Saxena
2004-02-11 6:51 ` Martin Diehl
2004-02-11 16:39 ` Deepak Saxena
2004-02-11 17:51 ` David S. Miller
2004-02-11 18:18 ` Matt Porter
2004-02-11 18:30 ` David S. Miller
2004-02-11 18:57 ` Deepak Saxena
2004-02-11 19:08 ` David S. Miller
2004-02-12 3:46 ` Deepak Saxena [this message]
2004-02-12 3:58 ` David S. Miller
2004-02-13 1:49 ` Jamie Lokier
2004-02-14 7:24 ` David S. Miller
2004-02-11 19:23 ` Matt Porter
2004-02-11 19:30 ` David S. Miller
2004-02-11 18:43 ` linux-2.6.2 Kernel Problem Elikster
2004-02-14 11:51 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 14:27 [Patch] dma_sync_to_device James Bottomley
2004-02-14 8:51 ` Martin Diehl
2004-02-14 22:34 ` James Bottomley
2004-02-14 23:18 ` David S. Miller
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=20040212034610.GA27317@plexity.net \
--to=dsaxena@plexity.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
--cc=mporter@kernel.crashing.org \
/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