From: Johannes Weiner <hannes@cmpxchg.org>
To: Hillf Danton <dhillf@gmail.com>
Cc: Michal Hocko <mhocko@suse.cz>, Ying Han <yinghan@google.com>,
linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: memcg: fix over reclaiming mem cgroup
Date: Wed, 25 Jan 2012 08:17:16 +0100 [thread overview]
Message-ID: <20120125071715.GA7694@cmpxchg.org> (raw)
In-Reply-To: <CAJd=RBDj5mtWJG0Byi=97Kuu6LnkwdndDO-AUpeYSCTBEy0P5A@mail.gmail.com>
On Wed, Jan 25, 2012 at 09:55:01AM +0800, Hillf Danton wrote:
> On Tue, Jan 24, 2012 at 4:23 PM, Michal Hocko <mhocko@suse.cz> wrote:
> > Barriered?
> >
> pushed out for 3.3-rc2 last night?
New features are only merged during the merge window (between 3.2 and
3.3-rc1), from then on it's only bugfixes to stabilize for release.
My soft limit patch missed this merge window, so the earliest target
is 3.4. And that's fine, there are still things that need to be
evaluated, like kswapd now reclaiming with priority 0 and
nr_to_reclaim at ULONG_MAX, which Michal pointed out. Or KAME's
concerns regarding direct soft reclaim and numa setups.
--
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-01-25 7:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 14:49 [PATCH] mm: memcg: fix over reclaiming mem cgroup Hillf Danton
2012-01-23 13:02 ` Michal Hocko
2012-01-23 19:14 ` Ying Han
2012-01-24 3:26 ` Hillf Danton
2012-01-24 8:23 ` Michal Hocko
2012-01-25 1:55 ` Hillf Danton
2012-01-25 7:17 ` Johannes Weiner [this message]
2012-01-24 23:50 ` Ying Han
2012-01-24 3:48 ` Balbir Singh
2012-01-24 8:30 ` Michal Hocko
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=20120125071715.GA7694@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=dhillf@gmail.com \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).