From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [never mind] kiobufs and highmem
Date: 23 Jul 2002 11:17:33 GMT [thread overview]
Message-ID: <slrnajqeqd.2q8.kraxel@bytesex.org> (raw)
In-Reply-To: 20020720003918.G758@nightmaster.csn.tu-chemnitz.de
> This should work. If you have highmem pages and your device can't
> handle >32-bit physical addresses, then kmap() them
> before pci_map_sg()ing them and kunmap() them after
> pci_unmap_sg()ing.
--verbose please, I don't see how kmap() will fix the 32-bit limit issue.
As far I know kmap() doesn't move the page in physical memory, but
creates a virtual mapping for it. Thus the kernel (i.e. the CPU) can
access it, but PCI busmasters still can't ...
Gerd
--
You can't please everybody. And usually if you _try_ to please
everybody, the end result is one big mess.
-- Linus Torvalds, 2002-04-20
prev parent reply other threads:[~2002-07-23 11:11 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
2002-07-19 22:39 ` Ingo Oeser
2002-07-23 11:17 ` Gerd Knorr [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=slrnajqeqd.2q8.kraxel@bytesex.org \
--to=kraxel@bytesex.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox