linux-kernel - Re: [PATCH] blk-throttle: Reset group slice when limits are changed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4D890CC1.7070602@fusionio.com>
Date:	Tue, 22 Mar 2011 21:55:29 +0100
From:	Jens Axboe <jaxboe@...ionio.com>
To:	Vivek Goyal <vgoyal@...hat.com>
CC:	Lina Lu <lulina_nuaa@...mail.com>,
	linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] blk-throttle: Reset group slice when limits are changed

On 2011-03-22 21:33, Vivek Goyal wrote:
> On Tue, Mar 15, 2011 at 01:54:56PM -0400, Vivek Goyal wrote:
>> Lina reported that if throttle limits are initially very high and then
>> dropped, then no new bio might be dispatched for a long time. And the
>> reason being that after dropping the limits we don't reset the existing
>> slice and do the rate calculation with new low rate and account the bios
>> dispatched at high rate. To fix it, reset the slice upon rate change.
> 
> Hi Jens,
> 
> Can you please apply this patch too.

Yep, applied. Thanks for the reminder :-)

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/