public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: Question about Zone Allocation 2.4.X
Date: Thu, 2 Jan 2003 16:11:27 -0800	[thread overview]
Message-ID: <20030103001127.GV9704@holomorphy.com> (raw)
In-Reply-To: <20030102181554.A21643@vger.timpanogas.org>

On Thu, Jan 02, 2003 at 06:15:54PM -0700, Jeff V. Merkey wrote:
> 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.

Adding new zone types is easy. Just add them to mmzone.h, avoid setting
->virtual (which does not universally exist) in free_area_init_core()
if it's not perma-mapped, stuff them in the fallback sequence in
build_zonelists(), and detect them in arch/*/mm/init.c


Bill

  reply	other threads:[~2003-01-03  0:03 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       ` Question " Jeff V. Merkey
2003-01-03  0:11         ` William Lee Irwin III [this message]
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=20030103001127.GV9704@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=jmerkey@timpanogas.org \
    --cc=jmerkey@vger.timpanogas.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