From: Jeff Moyer <jmoyer@redhat.com>
To: Corrado Zoccolo <czoccolo@gmail.com>
Cc: "Linux-Kernel" <linux-kernel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [RFC V2 PATCH 4/5] cfq-iosched: enable idling for last queue on priority class
Date: Wed, 21 Oct 2009 12:12:27 -0400 [thread overview]
Message-ID: <x4963a8915g.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <200910202012.21469.czoccolo@gmail.com> (Corrado Zoccolo's message of "Tue, 20 Oct 2009 20:12:21 +0200")
Corrado Zoccolo <czoccolo@gmail.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@gmail.com>
This looks OK at first glance.
Cheers,
Jeff
prev parent reply other threads:[~2009-10-21 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 18:12 Corrado Zoccolo
2009-10-21 16:12 ` Jeff Moyer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x4963a8915g.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=czoccolo@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome