public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: David Horner <ds2horner@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] writeback: dirty position control
Date: Wed, 17 Aug 2011 20:35:06 +0800	[thread overview]
Message-ID: <20110817123506.GA15403@localhost> (raw)
In-Reply-To: <20110817120356.GG9959@quack.suse.cz>

On Wed, Aug 17, 2011 at 08:03:56PM +0800, Jan Kara wrote:
> On Wed 17-08-11 02:40:19, David Horner wrote:
> >  I noticed a significant typo below (another of those thousand eyes,
> > thanks to Jan Kara's post that started ne looking) :
> > 
> >  > +static unsigned long bdi_position_ratio(struct backing_dev_info *bdi,
> >  > + unsigned long thresh,
> > ...
> >  > + * For JBOD case, bdi_thresh (not bdi_dirty!) could fluctuate up to its
> >  > + * own size, so move the slope over accordingly.
> >  > + */
> >  > + if (unlikely(bdi_thresh > thresh))
> >  > + bdi_thresh = thresh;
> >  > + /*
> >  > + * scale global setpoint to bdi's:  setpoint *= bdi_thresh / thresh
> >  > + */
> >  > + x = div_u64((u64)bdi_thresh << 16, thresh | 1);
> > 
> >                   ^
> >  I believe should be
> > 
> >     x = div_u64((u64)bdi_thresh << 16, thresh + 1);
>   I've noticed this as well but it's mostly a consistency issue. 'thresh'
> is going to be large in practice so there's not much difference between
> thresh + 1 and thresh | 1.

Right :) Anyway I'll change it to thresh + 1.

Thanks,
Fengguang

  reply	other threads:[~2011-08-17 12:35 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFdhcLRKvfqBnXCXLwq-Qe1eNAGC-8XJ3BtHpQKzaa3RhHyp6A@mail.gmail.com>
2011-08-17  6:40 ` [PATCH 2/5] writeback: dirty position control David Horner
2011-08-17 12:03   ` Jan Kara
2011-08-17 12:35     ` Wu Fengguang [this message]
2011-08-16  2:20 [PATCH 0/5] IO-less dirty throttling v9 Wu Fengguang
2011-08-16  2:20 ` [PATCH 2/5] writeback: dirty position control Wu Fengguang
2011-08-16 19:41   ` Jan Kara
2011-08-17 13:23     ` Wu Fengguang
2011-08-17 13:49       ` Wu Fengguang
2011-08-17 20:24       ` Jan Kara
2011-08-18  4:18         ` Wu Fengguang
2011-08-18  4:41           ` Wu Fengguang
2011-08-18 19:16           ` Jan Kara
2011-08-24  3:16         ` Wu Fengguang
2011-08-19  2:53   ` Vivek Goyal
2011-08-19  3:25     ` Wu Fengguang
  -- strict thread matches above, loose matches on Subject: below --
2011-08-06  8:44 [PATCH 0/5] IO-less dirty throttling v8 Wu Fengguang
2011-08-06  8:44 ` [PATCH 2/5] writeback: dirty position control Wu Fengguang
2011-08-08 13:46   ` Peter Zijlstra
2011-08-08 14:11     ` Wu Fengguang
2011-08-08 14:31       ` Peter Zijlstra
2011-08-08 22:47         ` Wu Fengguang
2011-08-09  9:31           ` Peter Zijlstra
2011-08-10 12:28             ` Wu Fengguang
2011-08-08 14:41       ` Peter Zijlstra
2011-08-08 23:05         ` Wu Fengguang
2011-08-09 10:32           ` Peter Zijlstra
2011-08-09 17:20           ` Peter Zijlstra
2011-08-10 22:34             ` Jan Kara
2011-08-11  2:29               ` Wu Fengguang
2011-08-11 11:14                 ` Jan Kara
2011-08-16  8:35                   ` Wu Fengguang
2011-08-12 13:19             ` Wu Fengguang
2011-08-10 21:40           ` Vivek Goyal
2011-08-16  8:55             ` Wu Fengguang
2011-08-11 22:56           ` Peter Zijlstra
2011-08-12  2:43             ` Wu Fengguang
2011-08-12  3:18               ` Wu Fengguang
2011-08-12  5:45               ` Wu Fengguang
2011-08-12  9:45                 ` Peter Zijlstra
2011-08-12 11:07                   ` Wu Fengguang
2011-08-12 12:17                     ` Peter Zijlstra
2011-08-12  9:47               ` Peter Zijlstra
2011-08-12 11:11                 ` Wu Fengguang
2011-08-12 12:54           ` Peter Zijlstra
2011-08-12 12:59             ` Wu Fengguang
2011-08-12 13:08               ` Peter Zijlstra
2011-08-12 13:04           ` Peter Zijlstra
2011-08-12 14:20             ` Wu Fengguang
2011-08-22 15:38               ` Peter Zijlstra
2011-08-23  3:40                 ` Wu Fengguang
2011-08-23 10:01                   ` Peter Zijlstra
2011-08-23 14:15                     ` Wu Fengguang
2011-08-23 17:47                       ` Vivek Goyal
2011-08-24  0:12                         ` Wu Fengguang
2011-08-24 16:12                           ` Peter Zijlstra
2011-08-26  0:18                             ` Wu Fengguang
2011-08-26  9:04                               ` Peter Zijlstra
2011-08-26 10:04                                 ` Wu Fengguang
2011-08-26 10:42                                   ` Peter Zijlstra
2011-08-26 10:52                                     ` Wu Fengguang
2011-08-26 11:26                                   ` Wu Fengguang
2011-08-26 12:11                                     ` Peter Zijlstra
2011-08-26 12:20                                       ` Wu Fengguang
2011-08-26 13:13                                         ` Wu Fengguang
2011-08-26 13:18                                           ` Peter Zijlstra
2011-08-26 13:24                                             ` Wu Fengguang
2011-08-24 18:00                           ` Vivek Goyal
2011-08-25  3:19                             ` Wu Fengguang
2011-08-25 22:20                               ` Vivek Goyal
2011-08-26  1:56                                 ` Wu Fengguang
2011-08-26  8:56                                   ` Peter Zijlstra
2011-08-26  9:53                                     ` Wu Fengguang
2011-08-29 13:12                             ` Peter Zijlstra
2011-08-29 13:37                               ` Wu Fengguang
2011-09-02 12:16                                 ` Peter Zijlstra
2011-09-06 12:40                                 ` Peter Zijlstra
2011-08-24 15:57                       ` Peter Zijlstra
2011-08-25  5:30                         ` Wu Fengguang
2011-08-23 14:36                     ` Vivek Goyal
2011-08-09  2:08   ` Vivek Goyal
2011-08-16  8:59     ` Wu Fengguang

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=20110817123506.GA15403@localhost \
    --to=fengguang.wu@intel.com \
    --cc=ds2horner@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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