From: Benjamin LaHaise <bcrl@redhat.com>
To: William D Waddington <csbwaddington@att.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [never mind] kiobufs and highmem
Date: Fri, 19 Jul 2002 11:32:58 -0400 [thread overview]
Message-ID: <20020719113258.B12183@redhat.com> (raw)
In-Reply-To: <ic9gju44p7ukriuv4etl0tdc5f6uf5s08m@4ax.com>; from csbwaddington@att.net on Fri, Jul 19, 2002 at 08:00:00AM -0700
On Fri, Jul 19, 2002 at 08:00:00AM -0700, William D Waddington wrote:
> Looks like three (?) options: go back to copying to a kernel DMA
> buffer for all cases (swell for performance), split the code path into
> map_user and copy_user branches (not that fond of spaghetti),
> or - in the highmem case - copy to a local buffer and populate the
> kiobuf with those pages and feed that to pci_map_sg().
Or use the PCI-DMA API function pci_map_single() that's documented in
Documentation/DMA-mapping.txt to get a 64 bit pointer? Don't forget to
do a pci_set_dma_mask too, but that's mentioned in DMA-mapping.txt.
-ben
--
"You will be reincarnated as a toad; and you will be much happier."
next prev parent reply other threads:[~2002-07-19 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 15:00 [never mind] kiobufs and highmem William D Waddington
2002-07-19 15:32 ` Benjamin LaHaise [this message]
2002-07-19 22:39 ` Ingo Oeser
2002-07-23 11:17 ` Gerd Knorr
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=20020719113258.B12183@redhat.com \
--to=bcrl@redhat.com \
--cc=csbwaddington@att.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.