From: Greg Thelen <gthelen@google.com>
To: lsf-pc@lists.linuxfoundation.org
Cc: linux-mm@kvack.org
Subject: [LSF/MM TOPIC] memcg aware writeback
Date: Fri, 04 Feb 2011 11:06:33 -0800 [thread overview]
Message-ID: <xr937hdf39hi.fsf@gthelen.mtv.corp.google.com> (raw)
In the MM Summit I would like to discuss pending memcg dirty limits changes and
especially how they will interact with writeback.
Once we have memcg dirty limits, we will face a new issue. When a memcg
dirty limit is crossed, writeback needs to bring the memcg back under
its dirty limit. Currently, writeback is unaware of memory controller.
Therefore writeback assumes that all dirty inodes are candidates for
memcg writeback. Our experience in Google production shows that doing
global (non cgroup aware) writeback substantially reduces isolation
between memory-hungry jobs.
If there was a way for memcg writeback to either avoid irrelevant inodes
or avoid irrelevant pages, then better isolation could be achieved.
We have been working on various designs to allow either page or inode
level filtering in the writeback code to achieve memcg-aware writeback.
I would like to have a discussion about these designs and see what
interest there is in this topic.
--
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:[~2011-02-04 19:06 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=xr937hdf39hi.fsf@gthelen.mtv.corp.google.com \
--to=gthelen@google.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linuxfoundation.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