From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Andrea Arcangeli <andrea@novell.com>, linux-kernel@vger.kernel.org
Subject: Re: ZONE_PADDING wastes 4 bytes of the new cacheline
Date: Fri, 22 Oct 2004 13:09:47 +1000 [thread overview]
Message-ID: <417879FB.5030604@yahoo.com.au> (raw)
In-Reply-To: <20041021182651.082e7f68.akpm@osdl.org>
Andrew Morton wrote:
> Andrea Arcangeli <andrea@novell.com> wrote:
>
>>I'm still unsure if the 2.6 lower_zone_protection completely mimics the
>> 2.4 lowmem_zone_reserve algorithm if tuned by reversing the pages_min
>> settings accordingly, but I believe it's easier to drop it and replace
>> with a clear understandable API that as well drops the pages_min levels
>> that have no reason to exists anymore
>
>
> I'd be OK with wapping over to the watermark version, as long as we have
> runtime-settable levels.
>
Please no "wapping" over :) This release is the first time the allocator
has been anywhere near working properly in this area.
Of course, if Andrea shows that the ->protection racket isn't sufficient,
then yeah.
> But I'd be worried about making the default values anything other than zero
> because nobody seems to be hitting the problems.
>
> But then again, this get discussed so infrequently that by the time it
> comes around again I've forgotten all the previous discussion. Ho hum.
>
I think they probably should be turned on. A system with a gig of ram
shouldn't be able to use up all of ZONE_DMA on pagecache. It seems like
a small price to pay... same goes for very big highmem systems and ZONE_NORMAL.
next prev parent reply other threads:[~2004-10-22 3:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 1:17 ZONE_PADDING wastes 4 bytes of the new cacheline Andrea Arcangeli
2004-10-21 3:10 ` Nick Piggin
2004-10-21 4:36 ` Andrew Morton
2004-10-21 4:53 ` Nick Piggin
2004-10-21 10:51 ` Mikael Pettersson
2004-10-21 12:45 ` Andrea Arcangeli
2004-10-21 18:54 ` Adam Heath
2004-10-21 20:21 ` DaMouse
2004-10-21 21:24 ` Jon Masters
2004-10-22 10:09 ` DaMouse
2004-10-21 22:26 ` Nick Piggin
2004-10-21 22:45 ` Andrea Arcangeli
2004-10-22 0:34 ` Nick Piggin
2004-10-22 1:10 ` Andrea Arcangeli
2004-10-22 1:26 ` Andrew Morton
2004-10-22 2:55 ` Jesse Barnes
2004-10-22 3:38 ` Nick Piggin
2004-10-22 3:49 ` Jesse Barnes
2004-10-22 17:15 ` Andrea Arcangeli
2004-10-22 3:09 ` Nick Piggin [this message]
2004-10-22 3:26 ` Andrew Morton
2004-10-22 3:35 ` Nick Piggin
2004-10-22 17:13 ` Andrea Arcangeli
2004-10-22 17:07 ` Andrea Arcangeli
2004-10-22 15:50 ` Andrea Arcangeli
2004-10-22 3:02 ` Nick Piggin
2004-10-22 16:58 ` Andrea Arcangeli
2004-10-23 4:33 ` Nick Piggin
2004-10-23 9:59 ` Andrea Arcangeli
2004-10-23 10:22 ` Nick Piggin
2004-10-23 11:03 ` Andrea Arcangeli
2004-10-23 16:28 ` Nick Piggin
2004-10-25 12:44 ` Andrea Arcangeli
2004-10-25 12:49 ` Nick Piggin
2004-10-25 13:51 ` Andrea Arcangeli
2004-10-25 20:09 ` Robert White
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=417879FB.5030604@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=andrea@novell.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.