From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mel Gorman <mel@skynet.ie>
Subject: Re: [PATCH] Configurable reclaim batch size
Date: Mon, 17 Sep 2007 21:56:15 +0200 [thread overview]
Message-ID: <20070917215615.685a5378@lappy> (raw)
In-Reply-To: <Pine.LNX.4.64.0709171053040.26860@schroedinger.engr.sgi.com>
On Mon, 17 Sep 2007 10:54:59 -0700 (PDT) Christoph Lameter
<clameter@sgi.com> wrote:
> On Sat, 15 Sep 2007, Peter Zijlstra wrote:
>
> > It increases the lock hold times though. Otoh it might work out with the
> > lock placement.
>
> Yeah may be good for NUMA.
Might, I'd just like a _little_ justification for an extra tunable.
> > Do you have any numbers that show this is worthwhile?
>
> Tried to run AIM7 but the improvements are in the noise. I need a tests
> that really does large memory allocation and stresses the LRU. I could
> code something up but then Lee's patch addresses some of the same issues.
> Is there any standard test that shows LRU handling regressions?
hehe, I wish. I was just hoping you'd done this patch as a result of an
actual problem and not a hunch.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mel Gorman <mel@skynet.ie>
Subject: Re: [PATCH] Configurable reclaim batch size
Date: Mon, 17 Sep 2007 21:56:15 +0200 [thread overview]
Message-ID: <20070917215615.685a5378@lappy> (raw)
In-Reply-To: <Pine.LNX.4.64.0709171053040.26860@schroedinger.engr.sgi.com>
On Mon, 17 Sep 2007 10:54:59 -0700 (PDT) Christoph Lameter
<clameter@sgi.com> wrote:
> On Sat, 15 Sep 2007, Peter Zijlstra wrote:
>
> > It increases the lock hold times though. Otoh it might work out with the
> > lock placement.
>
> Yeah may be good for NUMA.
Might, I'd just like a _little_ justification for an extra tunable.
> > Do you have any numbers that show this is worthwhile?
>
> Tried to run AIM7 but the improvements are in the noise. I need a tests
> that really does large memory allocation and stresses the LRU. I could
> code something up but then Lee's patch addresses some of the same issues.
> Is there any standard test that shows LRU handling regressions?
hehe, I wish. I was just hoping you'd done this patch as a result of an
actual problem and not a hunch.
--
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-09-17 19:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 22:23 [PATCH] Configurable reclaim batch size Christoph Lameter
2007-09-14 22:23 ` Christoph Lameter
2007-09-14 23:20 ` Peter Zijlstra
2007-09-14 23:20 ` Peter Zijlstra
2007-09-17 17:54 ` Christoph Lameter
2007-09-17 17:54 ` Christoph Lameter
2007-09-17 19:56 ` Peter Zijlstra [this message]
2007-09-17 19:56 ` Peter Zijlstra
2007-09-17 20:05 ` Christoph Lameter
2007-09-17 20:05 ` Christoph Lameter
2007-09-17 20:48 ` Balbir Singh
2007-09-17 20:48 ` Balbir Singh
2007-09-17 21:24 ` Christoph Lameter
2007-09-17 21:24 ` Christoph Lameter
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=20070917215615.685a5378@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
/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.