From: William Lee Irwin III <wli@holomorphy.com>
To: Scott Kaplan <sfkaplan@cs.amherst.edu>
Cc: linux-mm@kvack.org
Subject: Re: Avoiding the highmem mess
Date: Fri, 30 Aug 2002 15:05:50 -0700 [thread overview]
Message-ID: <20020830220550.GV18114@holomorphy.com> (raw)
In-Reply-To: <0334AD85-BC63-11D6-B00B-000393829FA4@cs.amherst.edu>
On Fri, Aug 30, 2002 at 05:54:09PM -0400, Scott Kaplan wrote:
> SO! To that end, I'd like to avoid the ZONE_HIGHMEM mess. It seems oddly
> done, and creates new kinds of contention between pools of pages that I
> don't want polluting my experiments. (That's not to say that I don't
> think it's a problem worth solving -- it's just not *the* problem that *I*
> want to examine just yet.)
You'll be fine if you keep physical memory down to less than the kernel
portion of the kernel/user split on 32-bit machines. In principle, if
there were a CONFIG_ISA to #undef and all you had were properly
functioning devices (e.g. no sound cards with only 24 lines wired) and
you could ignore it. OTOH it can be ignored anyway for the most part as
it's a very small pool and not heavily used unless your hardware is bad.
It probably won't be that much of an issue as 2.5.32-bk and/or -mm2 has
separate queues per-zone.
Cheers,
Bill
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2002-08-30 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 21:54 Scott Kaplan
2002-08-30 21:59 ` Andrew Morton
2002-08-30 22:05 ` William Lee Irwin III [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=20020830220550.GV18114@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-mm@kvack.org \
--cc=sfkaplan@cs.amherst.edu \
/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