From: Dan Malek <dan@mvista.com>
To: paulus@samba.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: pci_dma_sync_single
Date: Fri, 19 Oct 2001 22:13:56 -0400 [thread overview]
Message-ID: <3BD0DDE4.9E87E2BE@mvista.com> (raw)
In-Reply-To: 15308.8725.416230.867981@cargo.ozlabs.ibm.com
Paul Mackerras wrote:
> There are basically two ways to get a dma_handle:
Right, and here is what happend....The comment first existed when
we were mapping uncached pages (for any reason, including
pci_alloc_consistent) into a VM space that was not mapped 1:1
with the kernel (it was actually vmalloc()'ed under the covers).
In this case, bus_to_virt() wouldn't work, then I changed it to
use iopa() to scan the page tables, so it worked again, then I
changed pci_alloc_consistent() to just change the attributes on
the individual pages, and now with large pages sizes I have to
allocate the non-1:1 VM space again. So, the code has changed
a bunch without me changing the comment :-). I'm going to
settle on large pages with the non-1:1 mapping again, for real,
for the last time. I'll change the comment to say the right thing.
I think you have the right end of the stick :-). You shouldn't
have to sync_single on alloc_consistent space, but I couldn't find
consistent use of all of these functions among existing drivers.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-10-20 2:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 12:03 pci_dma_sync_single Paul Mackerras
2001-10-16 13:12 ` pci_dma_sync_single Ralph Blach
2001-10-16 14:08 ` pci_dma_sync_single Benjamin Herrenschmidt
2001-10-20 2:04 ` pci_dma_sync_single Dan Malek
2001-10-17 1:47 ` pci_dma_sync_single Paul Mackerras
2001-10-17 14:26 ` pci_dma_sync_single Tom Rini
2001-10-17 14:34 ` pci_dma_sync_single Ralph Blach
2001-10-20 2:13 ` Dan Malek [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=3BD0DDE4.9E87E2BE@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).