From: Wu Fengguang <fengguang.wu@intel.com>
To: lsf-pc@lists.linux-foundation.org
Cc: Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: [LSF/MM][ATTEND] readahead and writeback
Date: Sun, 5 Feb 2012 23:00:59 +0800 [thread overview]
Message-ID: <20120205150059.GA32739@localhost> (raw)
I would like to attend to participate in the readahead and writeback
discussions. My questions are
- readahead size and alignment, hope that we can reach some general
agreements on the policy stuff
- async write I/O bandwidth controller, will it be a good complement
feature to the current blk-cgroup I/O controller? Each seem to have
its own strong areas and weak points.
- per-memcg dirty pages control, to be frank, it's non-trivial to
implement and I'm not sure it will perform well in some cases.
Before following that direction, I'm curious whether the much more
simple scheme of moving dirty pages to the global LRU can magically
satisfy the main user demands.
Thanks,
Fengguang
--
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>
reply other threads:[~2012-02-05 15:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120205150059.GA32739@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).