From: Suresh Jayaraman <sjayaraman@suse.com>
To: Tejun Heo <tj@kernel.org>
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: Mon, 28 Jan 2013 17:16:30 +0530 [thread overview]
Message-ID: <51066516.4000501@suse.com> (raw)
In-Reply-To: <20130125175711.GJ3081@htj.dyndns.org>
On 01/25/2013 11:27 PM, Tejun Heo wrote:
> 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.
Ah, ok. Even if we have a way to check if in a particular cgroup all I/O
is async or not, I have feeling that sync latencies might still get
impacted for e.g. if we have a very few sync tasks plus many async tasks
in one cgroup competing with all sync tasks in another group or some
other combinations, no?
Thanks
--
Suresh Jayaraman
prev parent reply other threads:[~2013-01-28 11:46 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
2013-01-28 11:46 ` Suresh Jayaraman [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=51066516.4000501@suse.com \
--to=sjayaraman@suse.com \
--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=tj@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.