From: Tejun Heo <tj@kernel.org>
To: Suresh Jayaraman <sjayaraman@suse.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
Fengguang Wu <fengguang.wu@intel.com>,
Andrea Righi <andrea@betterlinux.com>,
Vivek Goyal <vgoyal@redhat.com>, Jan Kara <jack@suse.cz>,
Moyer Jeff Moyer <jmoyer@redhat.com>
Subject: Re: [LSF/MM TOPIC] [ATTEND] Throttling I/O
Date: Fri, 25 Jan 2013 09:57:11 -0800 [thread overview]
Message-ID: <20130125175711.GJ3081@htj.dyndns.org> (raw)
In-Reply-To: <51028666.1080109@suse.com>
Hey, Suresh.
On Fri, Jan 25, 2013 at 06:49:34PM +0530, Suresh Jayaraman wrote:
> - Making cfq schedule the per cgroup sync/async queues according to I/O
> weights would mean that we'll need to use per cgroup cfqq's instead
> of per process? What will the impact on sync latencies if for example
> we have many sync only tasks in one cgroup and many async tasks in
> another? What if BLK_CGROUP is not configured, what would be the
> fallback behavior?
So, we currently have synd cfqqs in cgroup cfqgs and shared cfqqs in
the root cfqg. The end result would be splitting shared cfqqs into
cgroup cfqgs. We may have to change how cfqgs are chosen depending on
whether it only has async IOs pending. Not sure.
> - Suppose if we have 100 cgroups and we are to have one cfqq per
> priority per cgroup, this would mean we'll be requiring 100 x 3 x 8 =
> 2400 cfqq's (3 classes and 8 priorities) in the worst case (as
> opposed to current 24 cfqqs)? This may not be as drastic as it sounds
> as we create cfqq's only on demand and we normally won't have tasks
> with every priority and every class?
I don't think that's a problem. We already have a cfqq per active IO
context which can go way beyond 10k depending on work load.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-01-25 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 13:19 [LSF/MM TOPIC] [ATTEND] Throttling I/O Suresh Jayaraman
2013-01-25 16:34 ` Vivek Goyal
2013-01-25 17:52 ` Tejun Heo
2013-01-25 18:26 ` Vivek Goyal
2013-01-25 18:33 ` Tejun Heo
2013-01-28 11:16 ` Suresh Jayaraman
2013-01-28 19:24 ` Tejun Heo
2013-01-25 17:57 ` Tejun Heo [this message]
2013-01-28 11:46 ` Suresh Jayaraman
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=20130125175711.GJ3081@htj.dyndns.org \
--to=tj@kernel.org \
--cc=andrea@betterlinux.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=sjayaraman@suse.com \
--cc=vgoyal@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).