From: Andrew Morton <akpm@zip.com.au>
To: Scott Kaplan <sfkaplan@cs.amherst.edu>
Cc: linux-mm@kvack.org
Subject: Re: Avoiding the highmem mess
Date: Fri, 30 Aug 2002 14:59:11 -0700 [thread overview]
Message-ID: <3D6FEAAF.E30967AD@zip.com.au> (raw)
In-Reply-To: <0334AD85-BC63-11D6-B00B-000393829FA4@cs.amherst.edu>
Scott Kaplan wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> ...
> Is there an easy way to avoid ZONE_HIGHMEM? Is it as easy as avoiding
> machines that have more than 1 GB of physical memory so that only
> ZONE_NORMAL is used?
Sure. Or just disable highmem in kernel config.
But be aware that since 2.5.32, the active/inactive lists are
per-zone. So you only ever have one type of page on each list.
Probably, this will simplify things.
--
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/
next prev parent reply other threads:[~2002-08-30 21:59 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 [this message]
2002-08-30 22:05 ` 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=3D6FEAAF.E30967AD@zip.com.au \
--to=akpm@zip.com.au \
--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