From: Michal Hocko <mhocko@suse.cz>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, "Li, Shaohua" <shaohua.li@intel.com>,
Christoph Hellwig <hch@lst.de>,
Dave Chinner <david@fromorbit.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Chris Mason <chris.mason@oracle.com>, Mel Gorman <mel@csn.ul.ie>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-mm <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] writeback: prevent bandwidth calculation overflow
Date: Mon, 22 Nov 2010 10:54:13 +0100 [thread overview]
Message-ID: <20101122095413.GA4231@tiehlicka.suse.cz> (raw)
In-Reply-To: <20101119184408.GA31113@localhost>
On Sat 20-11-10 02:44:08, Wu Fengguang wrote:
> On Sat, Nov 20, 2010 at 12:06:53AM +0800, Michal Hocko wrote:
> > On Fri 19-11-10 00:13:56, Wu Fengguang wrote:
> > > On Fri, Nov 19, 2010 at 12:02:01AM +0800, Peter Zijlstra wrote:
> > > > On Thu, 2010-11-18 at 23:44 +0800, Wu Fengguang wrote:
> > > > > + pause = HZ * pages_dirtied / (bw + 1);
> > > >
> > > > Shouldn't that be using something like div64_u64 ?
> > >
> > > Thanks for review. Here is the updated patch using div64_u64().
> > >
> > > ---
> > > Subject: writeback: prevent bandwidth calculation overflow
> > > Date: Thu Nov 18 12:55:42 CST 2010
> > >
> > > On 32bit kernel, bdi->write_bandwidth can express at most 4GB/s.
> > >
> > > However the current calculation code can overflow when disk bandwidth
> > > reaches 800MB/s. Fix it by using "long long" and div64_u64() in the
> > > calculations.
> > >
> > > And further change its unit from bytes/second to pages/second.
> > > That allows up to 16TB/s bandwidth in 32bit kernel.
> > >
> > > CC: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > Acked-by: Rik van Riel <riel@redhat.com>
> > > Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> > > ---
> > > mm/backing-dev.c | 4 ++--
> > > mm/page-writeback.c | 11 +++++------
> > > 2 files changed, 7 insertions(+), 8 deletions(-)
> > >
> > > --- linux-next.orig/mm/page-writeback.c 2010-11-18 12:42:58.000000000 +0800
> > > +++ linux-next/mm/page-writeback.c 2010-11-19 00:08:23.000000000 +0800
> > > @@ -494,7 +494,7 @@ void bdi_update_write_bandwidth(struct b
> > > unsigned long written;
> > > unsigned long elapsed;
> > > unsigned long bw;
> > > - unsigned long w;
> > > + unsigned long long w;
> > >
> > > if (*bw_written == 0)
> > > goto snapshot;
> > > @@ -513,7 +513,7 @@ void bdi_update_write_bandwidth(struct b
> > > goto snapshot;
> > >
> > > written = percpu_counter_read(&bdi->bdi_stat[BDI_WRITTEN]) - *bw_written;
> > > - bw = (HZ * PAGE_CACHE_SIZE * written + elapsed/2) / elapsed;
> > > + bw = (HZ * written + elapsed/2) / elapsed;
> >
> > Sorry for a dumb question, but where did PAGE_CACHE_SIZE part go?
>
> Because write_bandwidth's unit is bumped from bytes/s to pages/s,
> so that it can express much higher bandwidth.
Ahh, I can see it now.
Thanks
--
Michal Hocko
L3 team
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
prev parent reply other threads:[~2010-11-22 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 6:57 Wu Fengguang
2010-11-18 14:27 ` Rik van Riel
2010-11-18 15:44 ` Wu Fengguang
2010-11-18 16:02 ` Peter Zijlstra
2010-11-18 16:06 ` Wu Fengguang
2010-11-18 16:22 ` Wu Fengguang
2010-11-18 16:36 ` Wu Fengguang
2010-11-18 16:29 ` Peter Zijlstra
2010-11-18 16:34 ` Wu Fengguang
2010-11-18 16:13 ` Wu Fengguang
2010-11-19 16:06 ` Michal Hocko
2010-11-19 18:44 ` Wu Fengguang
2010-11-22 9:54 ` Michal Hocko [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=20101122095413.GA4231@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.com \
--cc=shaohua.li@intel.com \
--cc=tytso@mit.edu \
/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
Powered by JetHome