linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Vladimir Davydov <vdavydov@parallels.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] Documentation/memcg: warn about incomplete kmemcg state
Date: Tue, 22 Apr 2014 11:25:08 +0200	[thread overview]
Message-ID: <20140422092508.GA29311@dhcp22.suse.cz> (raw)
In-Reply-To: <1398066420-30707-1-git-send-email-vdavydov@parallels.com>

On Mon 21-04-14 11:47:00, Vladimir Davydov wrote:
> Kmemcg is currently under development and lacks some important features.
> In particular, it does not have support of kmem reclaim on memory
> pressure inside cgroup, which practically makes it unusable in real
> life. Let's warn about it in both Kconfig and Documentation to prevent
> complaints arising.
> 
> Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>

Thanks! This should have been merged log time ago...

Acked-by: Michal Hocko <mhocko@suse.cz>

> ---
>  Documentation/cgroups/memory.txt |    5 +++++
>  init/Kconfig                     |    6 ++++++
>  2 files changed, 11 insertions(+)
> 
> diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
> index 2622115276aa..af3cdfa3c07a 100644
> --- a/Documentation/cgroups/memory.txt
> +++ b/Documentation/cgroups/memory.txt
> @@ -270,6 +270,11 @@ When oom event notifier is registered, event will be delivered.
>  
>  2.7 Kernel Memory Extension (CONFIG_MEMCG_KMEM)
>  
> +WARNING: Current implementation lacks reclaim support. That means allocation
> +	 attempts will fail when close to the limit even if there are plenty of
> +	 kmem available for reclaim. That makes this option unusable in real
> +	 life so DO NOT SELECT IT unless for development purposes.
> +
>  With the Kernel memory extension, the Memory Controller is able to limit
>  the amount of kernel memory used by the system. Kernel memory is fundamentally
>  different than user memory, since it can't be swapped out, which makes it
> diff --git a/init/Kconfig b/init/Kconfig
> index 427ba60d638f..4d6e645c8ad4 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -993,6 +993,12 @@ config MEMCG_KMEM
>  	  the kmem extension can use it to guarantee that no group of processes
>  	  will ever exhaust kernel resources alone.
>  
> +	  WARNING: Current implementation lacks reclaim support. That means
> +	  allocation attempts will fail when close to the limit even if there
> +	  are plenty of kmem available for reclaim. That makes this option
> +	  unusable in real life so DO NOT SELECT IT unless for development
> +	  purposes.
> +
>  config CGROUP_HUGETLB
>  	bool "HugeTLB Resource Controller for Control Groups"
>  	depends on RESOURCE_COUNTERS && HUGETLB_PAGE
> -- 
> 1.7.10.4
> 

-- 
Michal Hocko
SUSE Labs

--
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>

      reply	other threads:[~2014-04-22  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21  7:47 [PATCH] Documentation/memcg: warn about incomplete kmemcg state Vladimir Davydov
2014-04-22  9:25 ` Michal Hocko [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=20140422092508.GA29311@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vdavydov@parallels.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).