From: Vivek Goyal <vgoyal@redhat.com>
To: Jens Axboe <jaxboe@fusionio.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: yummylln@yahoo.com.cn
Subject: Re: [PATCH] blk-throttle: Fix calculation of max number of WRITES to be dispatched
Date: Mon, 15 Nov 2010 10:28:02 -0500 [thread overview]
Message-ID: <20101115152802.GG30792@redhat.com> (raw)
In-Reply-To: <20101027172941.GD12981@redhat.com>
On Wed, Oct 27, 2010 at 01:29:41PM -0400, Vivek Goyal wrote:
> o Currently we try to dispatch more READS and less WRITES (75%, 25%) in one
> dispatch round. ummy pointed out that there is a bug in max_nr_writes
> calculation. This patch fixes it.
>
> Reported-by: ummy y <yummylln@yahoo.com.cn>
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
> ---
Hi Jens,
Do you have any concerns about this patch? If not, can you please apply
it.
Thanks
Vivek
> block/blk-throttle.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6/block/blk-throttle.c
> ===================================================================
> --- linux-2.6.orig/block/blk-throttle.c 2010-10-27 10:57:25.000000000 -0400
> +++ linux-2.6/block/blk-throttle.c 2010-10-27 11:02:33.733048194 -0400
> @@ -645,7 +645,7 @@ static int throtl_dispatch_tg(struct thr
> {
> unsigned int nr_reads = 0, nr_writes = 0;
> unsigned int max_nr_reads = throtl_grp_quantum*3/4;
> - unsigned int max_nr_writes = throtl_grp_quantum - nr_reads;
> + unsigned int max_nr_writes = throtl_grp_quantum - max_nr_reads;
> struct bio *bio;
>
> /* Try to dispatch 75% READS and 25% WRITES */
next prev parent reply other threads:[~2010-11-15 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 17:29 [PATCH] blk-throttle: Fix calculation of max number of WRITES to be dispatched Vivek Goyal
2010-11-15 15:28 ` Vivek Goyal [this message]
2010-11-15 18:33 ` 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=20101115152802.GG30792@redhat.com \
--to=vgoyal@redhat.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yummylln@yahoo.com.cn \
/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.