From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: William Lee Irwin III <wli@holomorphy.com>,
linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Cc: jmerkey@timpanogas.org
Subject: Re: Question about Zone Allocation 2.4.X
Date: Thu, 2 Jan 2003 18:15:54 -0700 [thread overview]
Message-ID: <20030102181554.A21643@vger.timpanogas.org> (raw)
In-Reply-To: <20030103000034.GU9704@holomorphy.com>; from wli@holomorphy.com on Thu, Jan 02, 2003 at 04:00:34PM -0800
On Thu, Jan 02, 2003 at 04:00:34PM -0800, William Lee Irwin III wrote:
> At some point in the past, I wrote:
> >> __get_free_pages() allocates from lowmem (i.e. 0-4GB) only.
> >> Allocate from highmem instead.
>
> 0-1GB. page_address() will give unpredictable results on highmem GFP masks.
Sounds broken to me.
>
> There is no GFP mask for it. Port Jens' ZONE_DMA32 or something, or roll
> ZONE_4G on your own if need be.
Bill,
Looks like we simply jetisioned the concept of a PPL (Physical Pages List)
and went with a zone allocator instead. I'm sure there was a good reason for
it historically. Rolling a separate zone is exactly what I was thinking
when I reviewed the code intially. Question, which files will be affected so when I put this one in, I don't end up breaking the VM and userspace balancing
logic. i.e. Could you point me to Jens' ZONE_DMA32 code as well.
Thanks
Jeff
>
>
> Bill
next prev parent reply other threads:[~2003-01-02 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 0:55 Questton about Zone Allocation 2.4.X Jeff V. Merkey
2003-01-02 23:51 ` William Lee Irwin III
2003-01-02 23:54 ` William Lee Irwin III
2003-01-03 1:08 ` Jeff V. Merkey
2003-01-03 0:00 ` William Lee Irwin III
2003-01-03 1:15 ` Jeff V. Merkey [this message]
2003-01-03 0:11 ` Question " William Lee Irwin III
2003-01-03 1:32 ` Jeff V. Merkey
2003-01-03 0:30 ` William Lee Irwin III
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=20030102181554.A21643@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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