From: Tejun Heo <tj@kernel.org>
To: Suresh Jayaraman <sjayaraman@suse.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
Fengguang Wu <fengguang.wu@intel.com>,
Andrea Righi <andrea@betterlinux.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 11:24:44 -0800 [thread overview]
Message-ID: <20130128192444.GE22465@mtj.dyndns.org> (raw)
In-Reply-To: <51065E1B.30209@suse.com>
Hey, Suresh.
On Mon, Jan 28, 2013 at 04:46:43PM +0530, Suresh Jayaraman wrote:
> > And I think tejun wanted to implement throttling at block layer and
> > wanted vm to adjust/respond to per group IO backlog when it comes
> > to writting to dirty data/inodes.
> >
> > Once we have take care of writeback problem then comes the issue
> > of being able to associate a dirty inode/page to a cgroup. Not sure
> > if something has happened on that front or not. In the past it was
> > thought to be simple that one inode belongs to one IO cgroup.
>
> Yes, this was discussed last year. But, not so much happened AFAIK.
Yeah, mostly because there were many more pressing issues around
cgroup and blkcg. Hierarchical support for cfq is now pending and a
lot of the foundation work for unified hierarchy (which IMHO is
essential for sane interaction between memcg and blkcg for writeback)
has been done, so it's getting there.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-01-28 19:24 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 [this message]
2013-01-25 17:57 ` Tejun Heo
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=20130128192444.GE22465@mtj.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).