All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Lina Lu <lulina_nuaa@foxmail.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Re: Re: blk-throttle.c : When limit is changed, must startanewslice
Date: Tue, 15 Mar 2011 11:04:05 -0400	[thread overview]
Message-ID: <20110315150405.GB24984@redhat.com> (raw)
In-Reply-To: <201103152300242189340@foxmail.com>

On Tue, Mar 15, 2011 at 11:00:25PM +0800, Lina Lu wrote:

[..]
> Hi Vivek,
> I have test the following patch on 2.6.39 core branch of Jens's tree, the bug has
> been fixed. 

Thanks Lina. I will cleanup this patch and post for inclusion.

> 
> Can you tell me which patch makes the throtl_tg_on_rr() return 1 even if the limits
> are very high?

Following patches fixes the issue in Jens's tree.

commit de701c74a34005e637e1ca2634fbf28fd1debba2
Author: Vivek Goyal <vgoyal@redhat.com>
Date:   Mon Mar 7 21:09:32 2011 +0100

    blk-throttle: Some cleanups and race fixes in limit  update code

Thanks
Vivek

      reply	other threads:[~2011-03-15 15:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_6A5F95FF2112DFE963C44E4E@qq.com>
2011-03-08 20:54 ` blk-throttle.c : When limit is changed, must start a new slice Vivek Goyal
2011-03-09 15:40 ` lulina_nuaa
2011-03-10 16:38 ` Lina Lu
2011-03-10 19:55   ` Vivek Goyal
2011-03-12 11:33   ` Re: Re: blk-throttle.c : When limit is changed, must start a newslice Lina Lu
2011-03-14 15:17     ` Vivek Goyal
2011-03-14 15:52     ` Re: Re: blk-throttle.c : When limit is changed, must start anewslice Lina Lu
2011-03-14 15:51       ` Vivek Goyal
2011-03-15 15:00       ` Re: Re: blk-throttle.c : When limit is changed, must startanewslice Lina Lu
2011-03-15 15:04         ` Vivek Goyal [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=20110315150405.GB24984@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lulina_nuaa@foxmail.com \
    /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.