From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Ying Han <yinghan@google.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] [ATTEND] memcg: soft limit reclaim (continue) and others
Date: Wed, 1 Feb 2012 13:54:42 +0900 [thread overview]
Message-ID: <20120201135442.0491d882.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <CALWz4iypV=k-7gVcFx=OsHJsWcUzQsfEoYbQ4+ySQoTob_PWcQ@mail.gmail.com>
On Tue, 31 Jan 2012 11:59:40 -0800
Ying Han <yinghan@google.com> wrote:
> some topics that I would like to discuss this year:
>
> 1) we talked about soft limit redesign during last LSF, and there are
> quite a lot of efforts and changes being pushed after that. I would
> like to take this time to sync-up our efforts and also discuss some of
> the remaining issues.
>
> Discussion from last year :
> http://www.spinics.net/lists/linux-mm/msg17102.html and lots of
> changes have been made since then.
>
Yes, it seems re-sync is required.
> 2) memory.stat, this is the main stat file for all memcg statistics.
> are we planning to keep stuff it for something like per-memcg
> vmscan_stat, vmstat or not.
>
Could you calrify ? Do you want to have another stat file like memory.vmstat ?
> 3) root cgroup now becomes quite interesting, especially after we
> bring back the exclusive lru to root. To be more specific, root cgroup
> now is like a sink which contains pages allocated on its own, and also
> pages being re-parented. Those pages won't be reclaimed until there is
> a global pressure, and we want to see anything we can do better.
>
I'm sorry I can't get your point.
Do you think it's better to shrink root mem cgroup LRU even if there are
no memory pressure ? The benefit will be reduced memory reclaim latency.
Or Do you think root memcg should have some soft limit and should be
reclaimed in the same schedule line as other memcgs ? The benefit will be fairness.
or other idea ?
Thanks,
-Kame
--
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 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 19:59 Ying Han
2012-02-01 4:54 ` KAMEZAWA Hiroyuki [this message]
2012-02-02 0:00 ` Ying Han
2012-02-10 3:44 ` KAMEZAWA Hiroyuki
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=20120201135442.0491d882.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--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