From: Greg Thelen <gthelen@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
"bsingharora@gmail.com" <bsingharora@gmail.com>,
Hugh Dickins <hughd@google.com>, Ying Han <yinghan@google.com>,
Mel Gorman <mgorman@suse.de>,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [LSF/MM TOPIC] memcg topics.
Date: Wed, 1 Feb 2012 12:24:25 -0800 [thread overview]
Message-ID: <CAHH2K0bPdqzpuWv82uyvEu4d+cDqJOYoHbw=GeP5OZk4-3gCUg@mail.gmail.com> (raw)
In-Reply-To: <20120201095556.812db19c.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, Jan 31, 2012 at 4:55 PM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> 4. dirty ratio
> In the last year, patches were posted but not merged. I'd like to hear
> works on this area.
I would like to attend to discuss this topic. I have not had much time to work
on this recently, but should be able to focus more on this soon. The
IO less writeback changes require some redesign and may allow for a
simpler implementation of mem_cgroup_balance_dirty_pages().
Maintaining a per container dirty page counts, ratios, and limits is
fairly easy, but integration with writeback is the challenge. My big
questions are for writeback people:
1. how to compute per-container pause based on bdi bandwidth, cgroup
dirty page usage.
2. how to ensure that writeback will engage even if system and bdi are
below respective background dirty ratios, yet a memcg is above its bg
dirty limit.
--
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 prev parent reply other threads:[~2012-02-01 20:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 0:55 KAMEZAWA Hiroyuki
2012-02-01 8:58 ` Glauber Costa
2012-02-02 11:33 ` [LSF/MM TOPIC][ATTEND] " Glauber Costa
2012-02-01 20:24 ` Greg Thelen [this message]
2012-02-02 6:33 ` [LSF/MM TOPIC] " Wu Fengguang
2012-02-02 7:34 ` Greg Thelen
2012-02-02 7:54 ` Wu Fengguang
2012-02-02 7:52 ` Wu Fengguang
2012-02-02 10:39 ` [Lsf-pc] " Jan Kara
2012-02-02 11:04 ` Wu Fengguang
2012-02-02 15:42 ` Jan Kara
2012-02-03 1:26 ` Wu Fengguang
2012-02-03 6:21 ` Greg Thelen
2012-02-03 9:40 ` Wu Fengguang
2012-02-02 10:15 ` Jan Kara
2012-02-02 11:31 ` Wu Fengguang
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='CAHH2K0bPdqzpuWv82uyvEu4d+cDqJOYoHbw=GeP5OZk4-3gCUg@mail.gmail.com' \
--to=gthelen@google.com \
--cc=bsingharora@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=yinghan@google.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