From: Tim Gardner <tim.gardner@canonical.com>
To: "Haefliger, Juerg" <Juerg.Haefliger@hp.com>
Cc: Vivek Goyal <vgoyal@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Block IO throttling disabled in distros
Date: Thu, 10 Feb 2011 12:21:58 -0700 [thread overview]
Message-ID: <4D543AD6.4000908@canonical.com> (raw)
In-Reply-To: <59DD1BA8FD3C0F4C90771C18F2B5B53A653FF72FB5@GVW0432EXB.americas.hpqcorp.net>
On 02/08/2011 12:24 AM, Haefliger, Juerg wrote:
>> On Mon, Feb 07, 2011 at 03:33:38PM +0000, Haefliger, Juerg wrote:
>>> Hi,
>>>
>>> Both RHEL6 and Ubuntu 10.10 have block IO throttling disabled in
>> their kernels. Does anybody know why that is? Are there performance or
>> stability issues with the throttling controller or does it somehow
>> negatively interfere with the rest of the kernel and/or system?
>>
>> Block IO throttling support was not even upstream at that time hence
>> you don't see it.
>
> Duh! I thought I checked that the code was there but just not enabled. I just double-checked and sure enough block IO throttling is not in the RHEL6 kernel source. Sorry for the noise.
>
> Thanks
> ...Juerg
>
>
>> I have not heard about any stability issues so far. Of course more
>> testing will reveal that.
>>
>> The only thing I have thinking is that should we limit the number of
>> bios queued per IO context on the device. Currently there is no such limit
>> and one can queue up as many bios as one want to.
>>
>>
>> Thanks
>> Vivek
> --
CONFIG_BLK_DEV_THROTTLING=y in what will be Ubuntu 11.04
rtg
--
Tim Gardner tim.gardner@canonical.com
prev parent reply other threads:[~2011-02-10 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 15:33 Block IO throttling disabled in distros Haefliger, Juerg
2011-02-07 16:04 ` Vivek Goyal
2011-02-08 7:24 ` Haefliger, Juerg
2011-02-10 19:21 ` Tim Gardner [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=4D543AD6.4000908@canonical.com \
--to=tim.gardner@canonical.com \
--cc=Juerg.Haefliger@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox