From: Vladimir Davydov <vdavydov@parallels.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Richard Davies <richard@arachsys.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org
Subject: Re: memcg with kmem limit doesn't recover after disk i/o causes limit to be hit
Date: Fri, 18 Apr 2014 22:37:09 +0400 [thread overview]
Message-ID: <535170D5.9090006@parallels.com> (raw)
In-Reply-To: <20140418182033.GA22235@dhcp22.suse.cz>
18.04.2014 22:20, Michal Hocko:
> On Fri 18-04-14 21:57:51, Vladimir Davydov wrote:
>> In short, kmem limiting for memory cgroups is currently broken. Do not
>> use it. We are working on making it usable though.
>
> Maybe we should make this explicit in both
> Documentation/cgroups/memory.txt and config MEMCG_KMEM help text.
Yeah, definitely. I'll send the patch.
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>
next prev parent reply other threads:[~2014-04-18 18:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 15:46 Richard Davies
2014-04-18 15:59 ` Michal Hocko
2014-04-18 17:57 ` Vladimir Davydov
2014-04-18 18:20 ` Michal Hocko
2014-04-18 18:37 ` Vladimir Davydov [this message]
2014-04-20 14:28 ` Protection against container fork bombs [WAS: Re: memcg with kmem limit doesn't recover after disk i/o causes limit to be hit] Richard Davies
2014-04-20 18:35 ` Tim Hockin
2014-04-22 18:39 ` Dwight Engen
2014-04-22 20:05 ` Richard Davies
2014-04-22 20:13 ` Tim Hockin
2014-04-23 6:07 ` Marian Marinov
2014-04-23 12:49 ` Dwight Engen
2014-04-28 18:00 ` Serge Hallyn
2014-04-29 7:25 ` Michal Hocko
2014-04-29 13:03 ` Serge Hallyn
2014-04-29 13:57 ` Marian Marinov
2014-04-29 14:04 ` Tim Hockin
2014-04-29 15:43 ` Michal Hocko
2014-04-29 16:06 ` Tim Hockin
2014-04-29 16:51 ` Frederic Weisbecker
2014-04-29 16:59 ` Tim Hockin
2014-04-29 17:06 ` Michal Hocko
2014-04-29 17:30 ` Dwight Engen
2014-04-29 18:09 ` Richard Davies
2014-04-29 18:27 ` Michal Hocko
2014-04-29 18:39 ` Richard Davies
2014-04-29 19:03 ` Michal Hocko
2014-04-29 21:36 ` Marian Marinov
2014-04-30 13:31 ` Michal Hocko
2014-04-29 21:44 ` Frederic Weisbecker
2014-04-30 13:12 ` Daniel J Walsh
2014-04-30 13:28 ` Frederic Weisbecker
2014-05-06 11:40 ` Marian Marinov
2014-05-07 17:15 ` Dwight Engen
2014-05-07 22:39 ` Marian Marinov
2014-05-08 15:25 ` Richard Davies
2014-06-10 14:50 ` Marian Marinov
2014-06-10 12:18 ` Alin Dobre
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=535170D5.9090006@parallels.com \
--to=vdavydov@parallels.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=richard@arachsys.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