From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org
Subject: Re: [RFC] VM batching patch problems?
Date: Sat, 28 Feb 2004 13:29:35 +1100 [thread overview]
Message-ID: <403FFD0F.60908@cyberone.com.au> (raw)
In-Reply-To: <403FF15E.3040800@cyberone.com.au>
Nick Piggin wrote:
>
> No it doesn't increase ZONE_NORMAL scanning. The scanning is the same
> rate,
> but because ZONE_NORMAL is 1/4 the size, it has quadruple the
> pressure. If
> you don't like logic, just pretend it is pinned by mem_map and other
> things.
> Your batching patch is conceptually wrong and it adds complexity.
>
An unfortunate typo. I was supposed to say "if you don't like *that* logic",
not "if you don't like logic"...
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2004-02-28 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 0:19 Nick Piggin
2004-02-28 0:52 ` Andrew Morton
2004-02-28 1:39 ` Nick Piggin
2004-02-28 1:49 ` Nick Piggin
2004-02-28 2:29 ` Nick Piggin [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=403FFD0F.60908@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.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