From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <christoph@lameter.com>
Cc: Jack Steiner <steiner@sgi.com>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [patch 1/4] pcp: zonequeues
Date: Wed, 13 Apr 2005 11:40:06 +1000 [thread overview]
Message-ID: <425C7876.9050302@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0504121202060.7576@graphe.net>
Christoph Lameter wrote:
> Seems that this also effectively addresses the issues raised with the
> pageset localization patches. Great work Nick!
>
I'd be interested to know what performance and lock contention
looks like on your larger systems, because we're using lru_lock
for the remote pageset... and there's only one of them.
Your interleaved pagecache allocation policy should be a good
brute force benchmark - just have one or two processes on each
node allocating pagecache pages (eg. from reading huge sparse
files).
The other thing is, you may want to look at adjusting the
criteria for using the remote pageset. It might be helpful to
use per-cpu pagesets on near remote nodes...
Nick
--
SUSE Labs, Novell Inc.
--
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:[~2005-04-13 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 13:23 Nick Piggin
2005-04-09 13:24 ` [patch 2/4] pcp: dynamic lists Nick Piggin
2005-04-09 13:24 ` [patch 3/4] pcp: NULL pagesets Nick Piggin
2005-04-09 13:25 ` [patch 4/4] pcp: only local pagesets Nick Piggin
2005-04-09 13:28 ` [patch 1/4] pcp: zonequeues Nick Piggin
2005-04-09 15:25 ` Nick Piggin
2005-04-12 16:15 ` Jack Steiner
2005-04-13 1:34 ` Nick Piggin
2005-04-12 19:02 ` Christoph Lameter
2005-04-13 1:40 ` 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=425C7876.9050302@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=christoph@lameter.com \
--cc=linux-mm@kvack.org \
--cc=steiner@sgi.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