From: Andi Kleen <andi@firstfloor.org>
To: Ying Han <yinghan@google.com>
Cc: Glauber Costa <glommer@parallels.com>,
Dave Chinner <dchinner@redhat.com>,
Rik van Riel <riel@redhat.com>, Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>, Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Greg Thelen <gthelen@google.com>,
Christoph Lameter <cl@linux.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/6] memcg: vfs isolation in memory cgroup
Date: Sat, 18 Aug 2012 20:41:20 -0700 [thread overview]
Message-ID: <m2vcgf8s67.fsf@firstfloor.org> (raw)
In-Reply-To: <CALWz4iw444F+odvnbrS_zfN_cNr0g+n3QBBTBtDGwZ8iJ89ujA@mail.gmail.com> (Ying Han's message of "Thu, 16 Aug 2012 22:40:02 -0700")
Ying Han <yinghan@google.com> writes:
>
> I haven't thought about the NUMA and node awareness for the shrinkers,
> and that sounds like something
> beyond than the problem I am trying to solve here. I might need to
> think a bit more of how that fits into the problem you described.
The memory failure code would also benefit from more directed slab
(especially d/icache) freeing method. Right now if it wants to hard/soft
offline a slab page it has to take the big hammer and free as much as it
can, just in the hope to free that one page.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
--
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>
next prev parent reply other threads:[~2012-08-19 3:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 20:53 [RFC PATCH 0/6] memcg: vfs isolation in memory cgroup Ying Han
2012-08-16 21:10 ` Rik van Riel
2012-08-16 23:41 ` Dave Chinner
2012-08-17 5:15 ` Glauber Costa
2012-08-17 5:40 ` Ying Han
2012-08-17 5:42 ` Glauber Costa
2012-08-17 7:56 ` Dave Chinner
2012-08-19 3:41 ` Andi Kleen [this message]
2012-08-17 7:54 ` Dave Chinner
2012-08-17 10:00 ` Glauber Costa
2012-08-17 19:18 ` Ying Han
2012-08-17 14:44 ` Rik van Riel
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=m2vcgf8s67.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=cl@linux.com \
--cc=dchinner@redhat.com \
--cc=glommer@parallels.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mhocko@suse.cz \
--cc=riel@redhat.com \
--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 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.