From: "David S. Miller" <davem@redhat.com>
To: adam@yggdrasil.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does kmalloc always return address below 4GB?
Date: Tue, 05 Mar 2002 03:59:14 -0800 (PST) [thread overview]
Message-ID: <20020305.035914.55508499.davem@redhat.com> (raw)
In-Reply-To: <200203051152.DAA05010@adam.yggdrasil.com>
In-Reply-To: <200203051152.DAA05010@adam.yggdrasil.com>
From: "Adam J. Richter" <adam@yggdrasil.com>
Date: Tue, 5 Mar 2002 03:52:14 -0800
| If you acquired your memory via the page allocator
| (i.e. __get_free_page*()) or the generic memory allocators
| (i.e. kmalloc() or kmem_cache_alloc()) then you may DMA to/from
| that memory using the addresses returned from those routines.
It might be a good idea to rephrase it. If I knew what that
sentence I would propose a patch to the DMA-mapping.txt file, but I
honestly don't know what proposition that sentence is supposed
to convey. If there really is no guarantee that this sentence is
conveying, then I guess the sentence should be deleted.
Probably it should qualify what it means with "and you used
GFP_KERNEL". Because that was the intention.
I'll fix that.
However, you can use GFP_HIGH memory with pci_map_page _iff_
you set your DMA mask to allow 64-bits.
The original impetus for that quoted bit of DMA-mapping.txt
was to make sure nobody used vmalloc() or kmap() pointers.
next prev parent reply other threads:[~2002-03-05 12:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 11:52 Does kmalloc always return address below 4GB? Adam J. Richter
2002-03-05 11:59 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 2:28 Adam J. Richter
2002-03-05 17:08 Adam J. Richter
2002-03-06 1:13 ` David S. Miller
2002-03-05 16:39 Adam J. Richter
2002-03-05 17:00 ` Gerd Knorr
2002-03-06 7:22 ` David S. Miller
2002-03-05 21:57 ` Steffen Persvold
2002-03-05 14:43 Adam J. Richter
2002-03-05 15:15 ` David S. Miller
2002-03-05 11:12 Adam J. Richter
2002-03-05 11:16 ` David S. Miller
2002-03-05 15:43 ` Steffen Persvold
2002-03-05 15:47 ` David S. Miller
2002-03-05 16:44 ` David Mosberger
2002-03-06 1:09 ` David S. Miller
2002-03-06 1:31 ` David Mosberger
2002-03-06 1:52 ` David S. Miller
2002-03-06 2:04 ` David Mosberger
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=20020305.035914.55508499.davem@redhat.com \
--to=davem@redhat.com \
--cc=adam@yggdrasil.com \
--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