From: Frederic Weisbecker <fweisbec@gmail.com>
To: Glauber Costa <glommer@parallels.com>
Cc: Michal Hocko <mhocko@suse.cz>,
akpm@linux-foundation.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: mmotm 2012-08-13-16-55 uploaded
Date: Thu, 23 Aug 2012 18:20:54 +0200 [thread overview]
Message-ID: <20120823162050.GB19305@somewhere.redhat.com> (raw)
In-Reply-To: <502A4410.6070201@parallels.com>
On Tue, Aug 14, 2012 at 04:26:56PM +0400, Glauber Costa wrote:
> On 08/14/2012 02:53 PM, Michal Hocko wrote:
> > On Mon 13-08-12 16:56:50, Andrew Morton wrote:
> >> > The mm-of-the-moment snapshot 2012-08-13-16-55 has been uploaded to
> >> >
> >> > http://www.ozlabs.org/~akpm/mmotm/
> > -mm git tree has been updated as well. You can find the tree at
> > https://github.com/mstsxfx/memcg-devel.git since-3.5
> >
> > tagged as mmotm-2012-08-13-16-55
> >
>
> On top of this tree, people following the kmemcg development may also
> want to checkout
>
> git://github.com/glommer/linux.git memcg-3.5/kmemcg-stack
>
> A branch called memcg-3.5/kmemcg-slab is also available with the slab
> changes ontop.
I tested it successfully to stop a forkbomb in a container.
One may need the following fix as well: http://marc.info/?l=linux-kernel&m=134573636430031&w=2
Andrew, others, what is your opinion on this patchset?
Thanks.
--
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:[~2012-08-23 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 23:56 mmotm 2012-08-13-16-55 uploaded akpm
2012-08-14 10:53 ` Michal Hocko
2012-08-14 12:26 ` Glauber Costa
2012-08-23 16:20 ` Frederic Weisbecker [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=20120823162050.GB19305@somewhere.redhat.com \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=glommer@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
/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).