From: "yunfeng zhang" <zyf.zeroos@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 2.6.20-rc5 1/1] MM: enhance Linux swap subsystem
Date: Sun, 25 Feb 2007 09:47:41 +0800 [thread overview]
Message-ID: <4df04b840702241747ne903699w636d37b40351b752@mail.gmail.com> (raw)
In-Reply-To: <45DE6080.6030904@redhat.com>
To a two-CPU architecture, its page distribution just like theoretically
ABABAB....
So every readahead of A process will create 4 unused readahead pages unless you
are sure B will resume soon.
Have you ever compared the results among UP, 2 or 4-CPU?
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-02-25 1:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4df04b840701212309l2a283357jbdaa88794e5208a7@mail.gmail.com>
[not found] ` <200701222300.41960.a1426z@gawab.com>
[not found] ` <4df04b840701222021w5e1aaab2if2ba7fc38d06d64b@mail.gmail.com>
[not found] ` <4df04b840701222108o6992933bied5fff8a525413@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0701242015090.1770@blonde.wat.veritas.com>
2007-01-29 5:29 ` [PATCH 2.6.20-rc5 1/1] MM: enhance Linux swap subsystem yunfeng zhang
[not found] ` <4df04b840701301852i41687edfl1462c4ca3344431c@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0701312022340.26857@blonde.wat.veritas.com>
2007-02-13 5:52 ` yunfeng zhang
2007-02-20 9:06 ` yunfeng zhang
2007-02-22 1:58 ` yunfeng zhang
2007-02-22 2:19 ` Rik van Riel
2007-02-23 2:31 ` yunfeng zhang
2007-02-23 3:33 ` Rik van Riel
2007-02-25 1:47 ` yunfeng zhang [this message]
2007-08-23 9:47 ` yunfeng zhang
2007-08-23 15:56 ` Randy Dunlap
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=4df04b840702241747ne903699w636d37b40351b752@mail.gmail.com \
--to=zyf.zeroos@gmail.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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).