linux-kernel - Re: [PATCH] Priorities in Anticipatory I/O scheduler

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 28 Oct 2008 10:14:20 -0700
From:	"Naveen Gupta" <ngupta@...gle.com>
To:	ngupta@...gle.com, linux-kernel@...r.kernel.org,
	jens.axboe@...cle.com, akpm@...ux-foundation.org
Subject: Re: [PATCH] Priorities in Anticipatory I/O scheduler

2008/10/27 Dave Chinner <david@...morbit.com>:
> On Mon, Oct 27, 2008 at 12:01:32PM -0700, ngupta@...gle.com wrote:
>>
>> Modifications to the Anticipatory I/O scheduler to add multiple priority
>> levels. It makes use of anticipation and batching in current
>> anticipatory scheduler to implement priorities.
>>
>> - Minimizes the latency of highest priority level.
>> - Low priority requests wait for high priority requests.
>> - Higher priority request break any anticipating low priority request.
>> - If single priority level is used the scheduler behaves as an
>>   anticipatory scheduler. So no change for existing users.
>>
>> With this change, it is possible for a latency sensitive job to coexist
>> with background job.
>>
>> Other possible use of this patch is in context of I/O subsystem controller.
>> It can add another dimension to the parameters controlling a particular cgroup.
>> While we can easily divide b/w among existing croups, setting a bound on
>> latency is not a feasible solution. Hence in context of storage devices
>> bandwidth and priority can be two parameters controlling I/O. Though
>> it can be a standalone patch to separate latency sensitive jobs and need
>> not be tied to I/O controller.
>>
>> In this patch I have added a new class IOPRIO_CLASS_LATENCY to differentiate
>> notion of absolute priority over existing uses of various time-slice based
>> priority classes in cfq. Though internally within anticipatory scheduler all
>> of them map to best-effort levels. Hence, one can also use various best-effort
>> priority levels.
>
> Please don't introduce yet another incompatible behaviour between
> I/O schedulers. It's bad enough from an optimisation point of view
> that BIO_RW_SYNC and BIO_RW_META mean different things to different
> schedulers, let alone that only CFQ currently understands
> priorities. If you are going to introduce priorities into AS, then
> please, please, please make it use the same interface as CFQ.
>
> Why? Both the extN and XFS devs have been considering bumping the
> priority of journal writes using the existing CFQ-based I/O priority
> mechanism - the last thing I want to see is a different scheduler
> requiring a different priority configuration to acheive the same
> optimisation. There is no way we can support this sort of
> optimisation in the filesystem code if the interface changes when
> the I/O scheduler changes. So please use the existing IOPRIO classes
> to map the priorities for the AS scheduler.
>

The anticipatory scheduler chooses it's next i/o to be of highest
available priority level. So, in some sense it kind of implements
absolute priority and is best used for jobs which are latency
sensitive.  Since the priorities can be and are mapped internally in
anticipatory scheduler, BEST_EFFORT class is mapped one-one with the
LATENCY class. A filesystem can use best-effort class using similar
interface as for cfq.

-Naveen


> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@...morbit.com
>
--
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/