linux-kernel - Re: [PATCH 0/4] cfq-iosched: policy fixes

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: <20091126090353.GR8742@kernel.dk>
Date:	Thu, 26 Nov 2009 10:03:53 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Corrado Zoccolo <czoccolo@...il.com>
Cc:	Linux-Kernel <linux-kernel@...r.kernel.org>,
	Jeff Moyer <jmoyer@...hat.com>, Vivek Goyal <vgoyal@...hat.com>
Subject: Re: [PATCH 0/4] cfq-iosched: policy fixes

On Tue, Nov 24 2009, Corrado Zoccolo wrote:
> Hi Jens,
> I've collected some bugfixes to the for-2.6.33 branch.
> Excluding the NCQ policy fix, that I'm resending with improved changelog,
> the bugs were found by Vivek while investingating performance drops
> or unfairness while testing cgroups. Nevertheless, those fixes have
> general impact, so they should go in before cgroup code is merged:
> * no-idle preemption logic was both under/over preempting.
>    it should preempt only if the active queue is idling due to
>    no-idle service tree empty
> * seeky queues with large depth could steal too much bandwidth to
>    low depth ones, so they will be marked as idling, and have exclusive
>    access to disk for their time share
> * the idling logic had some corner cases in which idling was not enabled,
>   even if it should have been, caused by rq_noidle and rq_in_driver checks.
>   Those were adjusted to better match the original intention.

Thanks Corrado, applied all 4!

-- 
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/