From: Divyesh Shah <dpshah@google.com>
To: Satoshi UCHIDA <s-uchida@ap.jp.nec.com>
Cc: linux-kernel@vger.kernel.org, ryov@valinux.co.jp,
axboe@kernel.dk, vtaras@openvz.org,
containers@lists.linux-foundation.org
Subject: Re: [patch 11/12][CFQ-cgroup] Control service tree: Main functions
Date: Mon, 16 Jun 2008 16:11:28 -0700 [thread overview]
Message-ID: <4F1784CD-6902-4A53-96E8-BE066C626B7D@google.com> (raw)
In-Reply-To: <1158affd-45fe-4257-a559-17a82883d92c@i36g2000prf.googlegroups.com>
> From: "Satoshi UCHIDA" <s-uch...@ap.jp.nec.com>
> Date: Apr 3, 12:20 am
> Subject: [patch 11/12][CFQ-cgroup] Control service tree: Main
> functions
>
> This patch introduced to control cfq_data.
> Its algorithm is similar to one when CFQ synchronous I/O.
>
> The new cfq optional operations:
> The "cfq_dispatch_requests_fn" defines a function which is implemented
> request dispatching algorithm.
> This becomes main function for fairness.
>
> The "cfq_completed_request_after_fn" defines a function which winds up
> I/O's
> affairs.
>
> The "cfq_active_check_fn" defines a function which make sure whether
> selecting cfq_data is equal to active cfq_data.
>
> The "cfq_empty_fn" defines a function which check whether active data
> exists.
>
> Signed-off-by:SatoshiUCHIDA<uch...@ap.jp.nec.com>
>
Hi Satoshi,
I was wondering if adding queue preemption to your design might
be useful.
If I understand correctly, currently if a higher priority cgroup is
only able to use
up a part of its time-slice (due to few requests) in a given round-
robin iteration,
it will need to wait for some other cgroups to get a shot at the disk
before it can get
its chance in the next iteration (though the residual timeslice helps
it get resorted to
a better position in the rr).
IMO, this high priority cgroup should have been able to get in and
send a few more requests
to disk till it uses up its remaining timeslice by preempting the
current lower priority cgroup.
This same argument can also be presented against CFQ but is more
valid here when we are working with
cgroups instead of individual processes as in production environments
collection of tasks which are
marked high-priority would often expect/require that level of
service. Also, something like this
could be implemented as a knob so that it can be turned on/off
depending on the use-case.
Does this make sense?
-Divyesh
parent reply other threads:[~2008-06-16 23:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1158affd-45fe-4257-a559-17a82883d92c@i36g2000prf.googlegroups.com>]
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=4F1784CD-6902-4A53-96E8-BE066C626B7D@google.com \
--to=dpshah@google.com \
--cc=axboe@kernel.dk \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryov@valinux.co.jp \
--cc=s-uchida@ap.jp.nec.com \
--cc=vtaras@openvz.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
all inboxes | Powered by JetHome®