linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Konstantin Khlebnikov <khlebnikov@openvz.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@suse.cz>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] mm/memcg: trivia and more lruvec
Date: Sun, 13 May 2012 21:58:18 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LSU.2.00.1205132152530.6148@eggly.anvils> (raw)

Here's a trivial renaming of two functions in Konstantin's patches;
some trivial little bits and pieces from my patches to vmscan.c now
on top of Konstantin's version; and the slightly more substantial
(but still functionally no different) use of lruvec instead of zone
pointer in lru_list functions.  Which I think takes us up to the
point beyond which Konstantin and I will need to settle differences
before proceeding further.

These I've diffed against 3.4.0-rc6-next-20120511, minus Ying's
"memcg: add mlock statistic in memory.stat" (and your fix to it)
that we already asked you to revert for now.

1/3 mm/memcg: get_lru_size not get_lruvec_size
2/3 mm: trivial cleanups in vmscan.c
3/3 mm/memcg: apply add/del_page to lruvec

 include/linux/memcontrol.h |   36 ++---------
 include/linux/mm_inline.h  |   20 +++---
 include/linux/swap.h       |    4 -
 mm/compaction.c            |    5 +
 mm/huge_memory.c           |    8 +-
 mm/memcontrol.c            |  111 +++++++++--------------------------
 mm/swap.c                  |   85 +++++++++++++-------------
 mm/vmscan.c                |   97 ++++++++++++++----------------
 8 files changed, 147 insertions(+), 219 deletions(-)

Hugh

--
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-05-14  4:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14  4:58 Hugh Dickins [this message]
2012-05-14  5:00 ` [PATCH 1/3] mm/memcg: get_lru_size not get_lruvec_size Hugh Dickins
2012-05-14 10:34   ` KAMEZAWA Hiroyuki
2012-05-14 10:44   ` Konstantin Khlebnikov
2012-05-14 15:49   ` Michal Hocko
2012-05-14  5:01 ` [PATCH 2/3] mm: trivial cleanups in vmscan.c Hugh Dickins
2012-05-14  5:56   ` KOSAKI Motohiro
2012-05-14 10:36   ` KAMEZAWA Hiroyuki
2012-05-14 10:46   ` Konstantin Khlebnikov
2012-05-14 15:52   ` Michal Hocko
2012-05-14  5:02 ` [PATCH 3/3] mm/memcg: apply add/del_page to lruvec Hugh Dickins
2012-05-14 10:40   ` KAMEZAWA Hiroyuki
2012-05-14 11:16   ` Konstantin Khlebnikov
2012-05-14 20:02     ` Hugh Dickins
2012-05-15  8:53       ` Konstantin Khlebnikov
2012-05-15 20:53         ` Hugh Dickins
2012-05-14 16:39   ` Michal Hocko
2012-05-15 12:34     ` Michal Hocko
2012-05-30 22:17   ` baozich
2012-05-31 22:58     ` Hugh Dickins
2012-05-31 19:14       ` Chen Baozi

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=alpine.LSU.2.00.1205132152530.6148@eggly.anvils \
    --to=hughd@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=khlebnikov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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