From: Andrea Arcangeli <aarcange@redhat.com>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [RFC][BUGFIX][PATCH 0/2] transhuge-memcg: some fixes (Re: Transparent Hugepage Support #25)
Date: Fri, 9 Jul 2010 18:48:15 +0200 [thread overview]
Message-ID: <20100709164815.GE5741@random.random> (raw)
In-Reply-To: <20100618132817.657f69b9.nishimura@mxp.nes.nec.co.jp>
On Fri, Jun 18, 2010 at 01:28:17PM +0900, Daisuke Nishimura wrote:
> Will do if necessary, but hmm, I heard from KAMEZAWA-san that he has already sent
> some patches to fix the similar problems on RHEL6, and I prefer his fixes to mine.
> Should I(or KAMEZAWA-san?) forward port his patches onto current aa.git ?
Now I also got more memcg fixes from Johannes... included in -27. It'd
be nice to keep things in sync.
http://www.kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.35-rc4/transparent_hugepage-27/memcg_check_room
http://www.kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.35-rc4/transparent_hugepage-27/memcg_consume_stock
http://www.kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.35-rc4/transparent_hugepage-27/memcg_oom
> Agreed. And I think you'll see some extra changes of memcg in 2.6.36...
> Any way, I'll do some test in both RHEL6 and aa.git when I have a time,
> and feel free to tell me if you have any troubles in back/forward porting
> memcg's fixes.
I just released a new #27, please use that. Thanks!
Andrea
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-07-09 16:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 0:05 Transparent Hugepage Support #25 Andrea Arcangeli
2010-05-21 3:26 ` Eric Dumazet
2010-05-21 3:26 ` Eric Dumazet
2010-05-21 5:13 ` Nick Piggin
2010-05-21 5:13 ` Nick Piggin
2010-06-02 5:44 ` [RFC][BUGFIX][PATCH 0/2] transhuge-memcg: some fixes (Re: Transparent Hugepage Support #25) Daisuke Nishimura
2010-06-02 5:44 ` Daisuke Nishimura
2010-06-02 5:45 ` [RFC][BUGFIX][PATCH 1/2] transhuge-memcg: fix for memcg compound Daisuke Nishimura
2010-06-02 5:45 ` Daisuke Nishimura
2010-06-02 5:46 ` [RFC][BUGFIX][PATCH 2/2] transhuge-memcg: commit tail pages at charge Daisuke Nishimura
2010-06-02 5:46 ` Daisuke Nishimura
2010-06-18 1:08 ` [RFC][BUGFIX][PATCH 0/2] transhuge-memcg: some fixes (Re: Transparent Hugepage Support #25) Andrea Arcangeli
2010-06-18 1:08 ` Andrea Arcangeli
2010-06-18 4:28 ` Daisuke Nishimura
2010-06-18 4:28 ` Daisuke Nishimura
2010-07-09 16:48 ` Andrea Arcangeli [this message]
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=20100709164815.GE5741@random.random \
--to=aarcange@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.