From: Jens Axboe <jens.axboe@oracle.com>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
"chris.mason" <chris.mason@oracle.com>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC PATCH] v2 mm: balance_dirty_pages. reduce calls to global_page_state to reduce cache references
Date: Mon, 7 Sep 2009 12:42:31 +0200 [thread overview]
Message-ID: <20090907104231.GR18599@kernel.dk> (raw)
In-Reply-To: <1252318290.2348.20.camel@castor>
On Mon, Sep 07 2009, Richard Kennedy wrote:
> On Sun, 2009-09-06 at 20:42 +0200, Jens Axboe wrote:
> > On Fri, Sep 04 2009, Richard Kennedy wrote:
> > > Reducing the number of times balance_dirty_pages calls global_page_state
> > > reduces the cache references and so improves write performance on a
> > > variety of workloads.
> > >
> > > 'perf stats' of simple fio write tests shows the reduction in cache
> > > access.
> > > Where the test is fio 'write,mmap,600Mb,pre_read' on AMD AthlonX2 with
> > > 3Gb memory (dirty_threshold approx 600 Mb)
> > > running each test 10 times, dropping the fasted & slowest values then
> > > taking
> > > the average & standard deviation
> > >
> > > average (s.d.) in millions (10^6)
> > > 2.6.31-rc8 648.6 (14.6)
> > > +patch 620.1 (16.5)
> >
> > This patch looks good to me, I have workloads too here where up to 10%
> > of the time is spent in balance_dirty_pages() because of this. I'll give
> > this patch a go on the box and test in question tomorrow, but it looks
> > promising.
> >
>
> Thanks Jens,
>
> It will be interesting to see how it works on different hardware &
> workload. How many cores are you going to run it on?
> wow 10% in balance_dirty_pages! Is that on a large server? or do you
> think its peculiar to your workload?
~10% is rounded, it was 8.9x%. Pretty bad! It's a 64-way, and there's
nothing special about the workload (just buffered IO with 4k blocks).
It's just going rather fast.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
"chris.mason" <chris.mason@oracle.com>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC PATCH] v2 mm: balance_dirty_pages. reduce calls to global_page_state to reduce cache references
Date: Mon, 7 Sep 2009 12:42:31 +0200 [thread overview]
Message-ID: <20090907104231.GR18599@kernel.dk> (raw)
In-Reply-To: <1252318290.2348.20.camel@castor>
On Mon, Sep 07 2009, Richard Kennedy wrote:
> On Sun, 2009-09-06 at 20:42 +0200, Jens Axboe wrote:
> > On Fri, Sep 04 2009, Richard Kennedy wrote:
> > > Reducing the number of times balance_dirty_pages calls global_page_state
> > > reduces the cache references and so improves write performance on a
> > > variety of workloads.
> > >
> > > 'perf stats' of simple fio write tests shows the reduction in cache
> > > access.
> > > Where the test is fio 'write,mmap,600Mb,pre_read' on AMD AthlonX2 with
> > > 3Gb memory (dirty_threshold approx 600 Mb)
> > > running each test 10 times, dropping the fasted & slowest values then
> > > taking
> > > the average & standard deviation
> > >
> > > average (s.d.) in millions (10^6)
> > > 2.6.31-rc8 648.6 (14.6)
> > > +patch 620.1 (16.5)
> >
> > This patch looks good to me, I have workloads too here where up to 10%
> > of the time is spent in balance_dirty_pages() because of this. I'll give
> > this patch a go on the box and test in question tomorrow, but it looks
> > promising.
> >
>
> Thanks Jens,
>
> It will be interesting to see how it works on different hardware &
> workload. How many cores are you going to run it on?
> wow 10% in balance_dirty_pages! Is that on a large server? or do you
> think its peculiar to your workload?
~10% is rounded, it was 8.9x%. Pretty bad! It's a 64-way, and there's
nothing special about the workload (just buffered IO with 4k blocks).
It's just going rather fast.
--
Jens Axboe
--
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:[~2009-09-07 10:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 11:05 [RFC PATCH] v2 mm: balance_dirty_pages. reduce calls to global_page_state to reduce cache references Richard Kennedy
2009-09-04 11:05 ` Richard Kennedy
2009-09-06 3:55 ` Wu Fengguang
2009-09-06 3:55 ` Wu Fengguang
2009-09-07 10:06 ` Richard Kennedy
2009-09-07 10:06 ` Richard Kennedy
2009-09-08 10:41 ` Richard Kennedy
2009-09-08 10:41 ` Richard Kennedy
2009-09-06 18:42 ` Jens Axboe
2009-09-06 18:42 ` Jens Axboe
2009-09-07 10:11 ` Richard Kennedy
2009-09-07 10:11 ` Richard Kennedy
2009-09-07 10:42 ` Jens Axboe [this message]
2009-09-07 10:42 ` Jens Axboe
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=20090907104231.GR18599@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard@rsk.demon.co.uk \
/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.