linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Ying Han <yinghan@google.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Minchan Kim <minchan.kim@gmail.com>,
	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Tejun Heo <tj@kernel.org>, Pavel Emelyanov <xemul@openvz.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Li Zefan <lizf@cn.fujitsu.com>, Mel Gorman <mel@csn.ul.ie>,
	Christoph Lameter <cl@linux.com>, Rik van Riel <riel@redhat.com>,
	Hugh Dickins <hughd@google.com>, Michal Hocko <mhocko@suse.cz>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	Zhu Yanhai <zhu.yanhai@gmail.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH] memcg: fix typo in the soft_limit stats.
Date: Tue, 17 May 2011 01:15:12 +0200	[thread overview]
Message-ID: <20110516231512.GW16531@cmpxchg.org> (raw)
In-Reply-To: <1305583230-2111-1-git-send-email-yinghan@google.com>

On Mon, May 16, 2011 at 03:00:30PM -0700, Ying Han wrote:
> This fixes the typo in the memory.stat including the following two
> stats:
> 
> $ cat /dev/cgroup/memory/A/memory.stat
> total_soft_steal 0
> total_soft_scan 0
> 
> And change it to:
> 
> $ cat /dev/cgroup/memory/A/memory.stat
> total_soft_kswapd_steal 0
> total_soft_kswapd_scan 0
> 
> Signed-off-by: Ying Han <yinghan@google.com>

I am currently proposing and working on a scheme that makes the soft
limit not only a factor for global memory pressure, but for
hierarchical reclaim in general, to prefer child memcgs during reclaim
that are in excess of their soft limit.

Because this means prioritizing memcgs over one another, rather than
having explicit soft limit reclaim runs, there is no natural counter
for pages reclaimed due to the soft limit anymore.

Thus, for the patch that introduces this counter:

Nacked-by: Johannes Weiner <hannes@cmpxchg.org>

--
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-05-16 23:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 22:00 Ying Han
2011-05-16 23:15 ` Johannes Weiner [this message]
2011-05-17  0:05   ` Ying Han
2011-05-17  0:13     ` Johannes Weiner
2011-05-17  0:18       ` Rik van Riel
2011-05-17  0:18     ` Andrew Morton
2011-05-17 23:49       ` KAMEZAWA Hiroyuki
2011-05-18  0:00         ` KAMEZAWA Hiroyuki
2011-05-18  0:56           ` Ying Han
2011-05-26  9:05       ` Johannes Weiner
2011-05-26 16:56         ` Ying Han

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=20110516231512.GW16531@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=cl@linux.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=hughd@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mel@csn.ul.ie \
    --cc=mhocko@suse.cz \
    --cc=minchan.kim@gmail.com \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=riel@redhat.com \
    --cc=tj@kernel.org \
    --cc=xemul@openvz.org \
    --cc=yinghan@google.com \
    --cc=zhu.yanhai@gmail.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