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: <x4963a8915g.fsf@segfault.boston.devel.redhat.com>
Date:	Wed, 21 Oct 2009 12:12:27 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Corrado Zoccolo <czoccolo@...il.com>
Cc:	"Linux-Kernel" <linux-kernel@...r.kernel.org>,
	Jens Axboe <jens.axboe@...cle.com>
Subject: Re: [RFC V2 PATCH 4/5] cfq-iosched: enable idling for last queue on priority class

Corrado Zoccolo <czoccolo@...il.com> writes:

> cfq can disable idling for queues in various circumstances.
> When workloads of different priorities are competing, if the higher
> priority queue has idling disabled, lower priority queues may steal
> its disk share. For example, in a scenario with an RT process
> performing seeky reads vs a BE process performing sequential reads,
> on an NCQ enabled hardware, with low_latency unset,
> the RT process will dispatch only the few pending requests every full
> slice of service for the BE process.
>
> The patch solves this issue by always performing idle on the last
> queue at a given priority class > idle. If the same process, or one
> that can pre-empt it (so at the same priority or higher), submits a
> new request within the idle window, the lower priority queue won't
> dispatch, saving the disk bandwidth for higher priority ones.
>
> Note: this doesn't touch the non_rotational + NCQ case (no hardware
> to test if this is a benefit in that case).
>
> Signed-off-by: Corrado Zoccolo <czoccolo@...il.com>

This looks OK at first glance.

Cheers,
Jeff
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ