[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#728110: marked as done (please enable CONFIG_BLK_DEV_THROTTLING in wheezy)



Your message dated Mon, 28 Oct 2013 16:54:31 +0000
with message-id <20131028165431.GH4583@decadent.org.uk>
and subject line Re: Bug#728109: please enable CONFIG_BLK_DEV_THROTTLING in wheezy
has caused the Debian Bug report #728109,
regarding please enable CONFIG_BLK_DEV_THROTTLING in wheezy
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
728109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728109
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.2.0-4-amd64
Version: 3.2.51-1
Severity: wishlist

Would you please consider enabling CONFIG_BLK_DEV_THROTTLING in wheezy's kernel?
Right now we have to recompile the kernel just to enable this feature :(
I see that it has already been enabled in 3.6.8-1~experimental.1 but how about
 stable? It is really useful for managing IO loads in virtualizaion environments
and since it requires an extra effort on the user's side to actually activate it
I don't think enabling it in the stable kernel will bring any disturbance to users
who don't intend to use it anyway.

Thanks and regards!
~George

--- End Message ---
--- Begin Message ---
On Mon, Oct 28, 2013 at 04:23:26PM +0200, Georgi Georgiev wrote:
> Package: linux-image-3.2.0-4-amd64
> Version: 3.2.51-1
> Severity: wishlist
> 
> Would you please consider enabling CONFIG_BLK_DEV_THROTTLING in wheezy's kernel?
> Right now we have to recompile the kernel just to enable this feature :(
> I see that it has already been enabled in 3.6.8-1~experimental.1 but how about
>  stable? It is really useful for managing IO loads in virtualizaion environments
> and since it requires an extra effort on the user's side to actually activate it
> I don't think enabling it in the stable kernel will bring any disturbance to users
> who don't intend to use it anyway.

Enabling this would change the module ABI, so it really is disruptive.
Newer kernel versions are available in wheezy-backports.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg

--- End Message ---

Reply to: