All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Kevin Wilson <wkevils-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: A problem with memory.oom_control
Date: Tue, 15 Apr 2014 10:49:41 +0800	[thread overview]
Message-ID: <534C9E45.9090005@huawei.com> (raw)
In-Reply-To: <CAGXs5wUdhEYQ-kGEPSD2A=OceZuA1tovLs04gPcRcqBPagQJCw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

于 2014/4/14 19:54, Kevin Wilson 写道:
> Hello,
> 
> First I hope this mailing list is the proper one for asking the
> following question:
> I do the following, as root,  on Fedora 20 with 3.12.7-300.fc20.x86_64 kernel:
> 
> create a cgroup called "0"
> /sys/fs/cgroup/memory/0
> 
> run:
> 
> echo "1" > /sys/fs/cgroup/memory/0/memory.oom_control
> bash: echo: write error: Invalid argument
> 
> Why am I having this error  ?
> 
> According to the documentation:
> 
> http://lxr.free-electrons.com/source/Documentation/cgroups/memory.txt
> this should work.
> 

Check if /sys/fs/cgroup/memory/memory/use_hierarchy is 1, if so the failure
is an expectecd bahavior.

"This operation is only allowed to the top cgroup of a sub-hierarchy."

  parent reply	other threads:[~2014-04-15  2:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 11:54 A problem with memory.oom_control Kevin Wilson
     [not found] ` <CAGXs5wUdhEYQ-kGEPSD2A=OceZuA1tovLs04gPcRcqBPagQJCw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-15  2:49   ` Li Zefan [this message]
     [not found]     ` <534C9E45.9090005-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-04-15  4:03       ` Kevin Wilson
     [not found]         ` <CAGXs5wVPsdPFm5EssN3_MSSermVMoUtAqc9XTH_YVN+bkPKVyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-15 11:05           ` William Dauchy
2014-04-30  8:56   ` 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=534C9E45.9090005@huawei.com \
    --to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wkevils-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.