From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: volodya@mindspring.com, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mm question
Date: Mon, 10 Dec 2001 09:16:53 -0800 [thread overview]
Message-ID: <2953465770.1007975813@mbligh.des.sequent.com> (raw)
In-Reply-To: <2953042101.1007975389@mbligh.des.sequent.com>
>>> > I was hoping for something more elegant, but I am not adverse to writing
>>> > my own get_free_page_from_range().
>>>
>>> Thats not a trivial task.
>>
>> Better than giving up.. Unfortunately looking around in
>> linux/Documentation and drivers did not yield much in terms of
>> explanation. I know I can use mem_map_reserve to reserve a page but I
>> don't know how to get page struct from a physical address nor which lock
>> to use when messing with this.
>
> If you don't have any ISA DMA going on in the system, you might consider
> bastardising the ZONE_DMA page range by moving the boundary up to
> 64Mb, then fixing the allocator not to fail back ZONE_NORMAL et al
> allocations to ZONE_DMA. Thus what was originally ZONE_DMA becomes
> a sort of ZONE_NO_DMA. Not in the slightest bit pretty, but it might be easier
> to implement. Depends if you ever want it to get back into the main tree,
> I guess ;-)
Of course, if you just did that, you'd never use the ZONE_DMA memory, so
that's pretty pointless ;-) You need to create an alloc call with an *option*
to force alloc out of ZONE_NORMAL, not make no fallback the default.
M.
next prev parent reply other threads:[~2001-12-10 17:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 13:25 volodya
2001-12-10 13:46 ` Alan Cox
2001-12-10 13:47 ` volodya
2001-12-10 14:07 ` Alan Cox
2001-12-10 15:03 ` volodya
2001-12-10 15:21 ` Alan Cox
2001-12-10 15:40 ` Rik van Riel
2001-12-10 16:14 ` volodya
2001-12-10 16:48 ` Rik van Riel
2001-12-10 17:02 ` volodya
2001-12-10 17:16 ` Alan Cox
2001-12-10 17:29 ` volodya
2001-12-10 18:05 ` Rik van Riel
2001-12-10 18:08 ` volodya
2001-12-10 18:17 ` Rik van Riel
2001-12-10 21:30 ` volodya
2001-12-10 18:26 ` Alan Cox
2001-12-10 21:27 ` volodya
2001-12-10 21:42 ` Alan Cox
2001-12-11 1:52 ` volodya
2001-12-11 8:47 ` Eric W. Biederman
2001-12-11 11:07 ` volodya
2001-12-11 18:39 ` Daniel Phillips
2001-12-10 16:05 ` volodya
2001-12-10 17:09 ` Martin J. Bligh
2001-12-10 17:16 ` Martin J. Bligh [this message]
2001-12-10 17:26 ` volodya
2001-12-10 17:25 ` Alan Cox
2001-12-10 17:38 ` volodya
2001-12-10 17:51 ` Alan Cox
2001-12-10 17:43 ` volodya
2001-12-10 18:12 ` Alan Cox
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=2953465770.1007975813@mbligh.des.sequent.com \
--to=martin.bligh@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=volodya@mindspring.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
all inboxes | Powered by JetHome®