From: Con Kolivas <kernel@kolivas.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
ck@vds.kolivas.org, Andrew Morton <akpm@osdl.org>,
linux list <linux-kernel@vger.kernel.org>
Subject: Re: lowmem_reserve question
Date: Mon, 3 Apr 2006 15:18:48 +1000 [thread overview]
Message-ID: <200604031518.49184.kernel@kolivas.org> (raw)
In-Reply-To: <1144041247.8198.8.camel@homer>
On Monday 03 April 2006 15:14, Mike Galbraith wrote:
> On Mon, 2006-04-03 at 14:48 +1000, Con Kolivas wrote:
> > On Monday 03 April 2006 14:42, Mike Galbraith wrote:
> > > On Mon, 2006-04-03 at 12:48 +1000, Con Kolivas wrote:
> > > > Furthermore, now that we have the option of up to 3GB lowmem split on
> > > > 32bit we can have a default lowmem_reserve of almost 12MB (if I'm
> > > > reading it right) which seems very tight with only 16MB of ZONE_DMA.
> > >
> > > I haven't crawled around in the vm for ages, but I think that's only
> > > 16MB if you support antique cards.
> >
> > That's what the ram is used for, but that is all the ZONE_DMA 32bit
> > machines get, whether you use it for that purpose or not. My concern is
> > that this will have all sorts of effects on the balancing since it will
> > always appear almost full.
>
> If that dinky 16MB zone still exists, and always appears nearly full, be
> happy. It used to be a real PITA.
That's not the point. If you try to do any allocation anywhere else it also
checks that zone, and it will find it full (always) leading to reclaim all
over the place for no good reason. This has nothing to do with actually
wanting to use that space or otherwise.
Cheers,
Con
next prev parent reply other threads:[~2006-04-03 5:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 4:01 2.6.16-ck3 Con Kolivas
2006-04-02 4:46 ` 2.6.16-ck3 Nick Piggin
2006-04-02 8:51 ` 2.6.16-ck3 Con Kolivas
2006-04-02 9:37 ` 2.6.16-ck3 Nick Piggin
2006-04-02 9:39 ` [ck] 2.6.16-ck3 Con Kolivas
2006-04-02 9:51 ` Nick Piggin
2006-04-03 2:48 ` lowmem_reserve question Con Kolivas
2006-04-03 4:42 ` Mike Galbraith
2006-04-03 4:48 ` Con Kolivas
2006-04-03 4:50 ` [ck] " Con Kolivas
2006-04-03 5:14 ` Mike Galbraith
2006-04-03 5:18 ` Con Kolivas [this message]
2006-04-03 5:31 ` Mike Galbraith
2006-04-04 2:35 ` [ck] " Con Kolivas
2006-04-06 1:10 ` [PATCH] mm: limit lowmem_reserve Con Kolivas
2006-04-06 1:29 ` Respin: " Con Kolivas
2006-04-06 2:43 ` Andrew Morton
2006-04-06 2:55 ` Con Kolivas
2006-04-06 2:58 ` Con Kolivas
2006-04-06 3:40 ` Andrew Morton
2006-04-06 4:36 ` Con Kolivas
2006-04-06 4:52 ` Con Kolivas
2006-04-07 6:25 ` Nick Piggin
2006-04-07 9:02 ` Con Kolivas
2006-04-07 12:40 ` Nick Piggin
2006-04-08 0:15 ` Con Kolivas
2006-04-08 0:55 ` Nick Piggin
2006-04-08 1:01 ` Con Kolivas
2006-04-08 1:25 ` Nick Piggin
2006-05-17 14:11 ` Con Kolivas
2006-05-18 7:11 ` Nick Piggin
2006-05-18 7:21 ` Con Kolivas
2006-05-18 7:26 ` Nick Piggin
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=200604031518.49184.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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;
as well as URLs for NNTP newsgroup(s).