From: Jes Sorensen <jes@sunsite.dk>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linux Bigot <linuxopinion@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: how to get virtual address from dma address
Date: 05 Oct 2001 16:06:31 +0200 [thread overview]
Message-ID: <d3n136tc48.fsf@lxplus014.cern.ch> (raw)
In-Reply-To: <200110032244.f93MiI103485@localhost.localdomain>
In-Reply-To: James Bottomley's message of "Wed, 03 Oct 2001 17:44:18 -0500"
>>>>> "James" == James Bottomley <James.Bottomley@HansenPartnership.com> writes:
Linux> All programmers I am relatively new to linux kernel. Please
Linux> advise what is the safe way to get the original virtaul address
Linux> from dma address e.g.,
>> You have to store the address you pass to pci_map_single()
>> somewhere in your data structures together with the dma address.
James> Yes, but speaking as someone who had to use a large hammer to
James> convert his driver from bus_to_virt et al., it does seem rather
James> hard not to have the equivalent for the new pci_dma paradigm.
James> It does present an obstacle persuading people to convert
James> drivers, particularly if the hardware is going to present a
James> linked list of addresses (as SCSI hardware often does).
Because as DaveM pointed out, some hardware can't do it, and as I said
earlier, it's a lot cheaper and easier for driver writers to just
store the extra pointer in their data structures than it is to
implement a database to maintain it.
Remember you often need this address in the hot path (say TX interrupt
handler) so you don't want to introduce any unnecessary function calls.
Jes
next prev parent reply other threads:[~2001-10-05 14:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 22:44 how to get virtual address from dma address James Bottomley
2001-10-04 0:24 ` David S. Miller
2001-10-04 10:11 ` BALBIR SINGH
2001-10-04 11:16 ` David S. Miller
2001-10-04 15:37 ` James Bottomley
2001-10-05 14:06 ` Jes Sorensen [this message]
2001-10-06 8:06 ` Paul Mackerras
2001-10-06 8:38 ` David S. Miller
2001-10-06 12:18 ` Paul Mackerras
2001-10-06 14:45 ` James Bottomley
2001-10-06 16:51 ` Gérard Roudier
2001-10-06 17:23 ` Jes Sorensen
2001-10-07 2:13 ` Paul Mackerras
2001-10-07 17:40 ` Jes Sorensen
2001-10-07 7:21 ` Gérard Roudier
2001-10-07 16:23 ` James Bottomley
2001-10-07 18:24 ` Gérard Roudier
2001-10-07 23:02 ` James Bottomley
2001-10-08 21:06 ` Gérard Roudier
[not found] ` <mailman.1002371041.9232.linux-kernel2news@redhat.com>
2001-10-06 18:19 ` Pete Zaitcev
[not found] ` <mailman.1002355920.6872.linux-kernel2news@redhat.com>
2001-10-06 18:04 ` Pete Zaitcev
[not found] <Pine.LNX.4.21.0110031525370.14852-100000@pogo.esscom.com>
2001-10-03 21:48 ` Linux Bigot
2001-10-03 22:03 ` Ben Collins
2001-10-05 14:04 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2001-10-03 21:30 Manfred Spraul
2001-10-03 16:37 Linux Bigot
2001-10-03 19:32 ` Ben Collins
2001-10-03 21:11 ` Linux Bigot
2001-10-03 21:23 ` Ben Collins
2001-10-03 14:11 Linux Bigot
2001-10-03 15:25 ` Jes Sorensen
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=d3n136tc48.fsf@lxplus014.cern.ch \
--to=jes@sunsite.dk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxopinion@yahoo.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