From: Suresh Jayaraman <sjayaraman@suse.com>
To: lsf-pc@lists.linux-foundation.org
Cc: Vivek Goyal <vgoyal@redhat.com>,
Andrea Righi <andrea@betterlinux.com>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Jan Kara <jack@suse.cz>
Subject: [ATTEND] [LSF/MM TOPIC] Buffered writes throttling
Date: Fri, 02 Mar 2012 12:48:43 +0530 [thread overview]
Message-ID: <4F507453.1020604@suse.com> (raw)
Committee members,
Please consider inviting me to the Storage, Filesystem, & MM Summit. I
am working for one of the kernel teams in SUSE Labs focusing on Network
filesystems and block layer.
Recently, I have been trying to solve the problem of "throttling
buffered writes" to make per-cgroup throttling of IO to the device
possible. Currently the block IO controller does not throttle buffered
writes. The writes would have lost the submitter's context (I/O comes in
flusher thread's context) when they are at the block IO layer. I looked
at the past work and many folks have attempted to solve this problem in
the past years but this problem remains unsolved so far.
First, Andrea Righi tried to solve this by limiting the rate of async
writes at the time a task is generating dirty pages in the page cache.
Next, Vivek Goyal tried to solve this by throttling writes at the time
they are entering the page cache.
Both these approches have limitations and not considered for merging.
I have looked at the possibility of solving this at the filesystem level
but the problem with ext* filesystems is that a commit will commit the
whole transaction at once (which may contain writes from
processes belonging to more than one cgroup). Making filesystems cgroup
aware would need redesign of journalling layer itself.
Dave Chinner thinks this problem should be solved and being solved in a
different manner by making the bdi-flusher writeback cgroup aware.
Greg Thelen's memcg writeback patchset (already been proposed for LSF/MM
summit this year) adds cgroup awareness to writeback. Some aspects of
this patchset could be borrowed for solving the problem of throttling
buffered writes.
As I understand the topic was discussed during last Kernel Summit as
well and the idea is to get the IO-less throttling patchset into the
kernel, then do per-memcg dirty memory limiting and add some memcg
awareness to writeback Greg Thelen and then when these things settle
down, think how to solve this problem since noone really seem to have a
good answer to it.
Having worked on linux filesystem/storage area for a few years now and
having spent time understanding the various approaches tried and looked
at other feasible way of solving this problem, I look forward to
participate in the summit and discussions.
So, the topic I would like to discuss is solving the problem of
"throttling buffered writes". This could considered for discussion with
memcg writeback session if that topic has been allocated a slot.
I'm aware that this is a late submission and my apologies for not making
it earlier. But, I want to take chances and see if it is possible still..
Thanks
Suresh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2012-03-02 7:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 7:18 Suresh Jayaraman [this message]
2012-03-02 15:33 ` [ATTEND] [LSF/MM TOPIC] Buffered writes throttling Vivek Goyal
2012-03-05 19:22 ` Fengguang Wu
2012-03-05 21:11 ` Vivek Goyal
2012-03-05 22:30 ` Fengguang Wu
2012-03-05 23:19 ` Andrea Righi
2012-03-05 23:51 ` Fengguang Wu
2012-03-06 0:46 ` Andrea Righi
2012-03-07 20:26 ` Vivek Goyal
2012-03-05 22:58 ` Andrea Righi
2012-03-07 20:52 ` Vivek Goyal
2012-03-07 22:04 ` Jeff Moyer
2012-03-08 8:08 ` Greg Thelen
2012-03-05 20:23 ` [Lsf-pc] " Jan Kara
2012-03-05 21:41 ` Vivek Goyal
2012-03-07 17:24 ` Jan Kara
2012-03-07 21:29 ` Vivek Goyal
2012-03-05 22:18 ` Vivek Goyal
2012-03-05 22:36 ` Jan Kara
2012-03-07 6:42 ` Fengguang Wu
2012-03-07 6:31 ` Fengguang Wu
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=4F507453.1020604@suse.com \
--to=sjayaraman@suse.com \
--cc=andrea@betterlinux.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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 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).