From: PINTU KUMAR <pintu.k-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bsingharora-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org,
mhocko-AlSwsSmVLrQ@public.gmane.org,
hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
Cc: cpgs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org
Subject: CGROUPS: HowTo: perform force_empty
Date: Mon, 02 Feb 2015 15:23:22 +0530 [thread overview]
Message-ID: <002d01d03ece$1971ae10$4c550a30$@samsung.com> (raw)
Hi,
I have a question about memory cgroups under Linux kernel 3.10.
Under: /sys/fs/cgroup/memory/:
I found, memory.force_empty.
But, when I try to do the following it says invalid argument:
# echo 0 > memory.force_empty
sh: echo: write error: Invalid argument
It even fails with "echo 1"
I am using this command from the shell using the root login.
Can you tell me how to execute the force_empty command.
Or, how to release all the memory under all cgroups and release it to the
system?
Under, mm/memcontrol.c , if I use the function: mem_cgroup_force_empty(struct
mem_cgroup *memcg), will it help to release all memory?
But, then, how to initialize the memcg data structure?
Can you provide some example to use this API, from some other kernel sub-system.
Thank you.
Regards,
Pintu
next reply other threads:[~2015-02-02 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 9:53 PINTU KUMAR [this message]
2015-02-02 12:15 ` CGROUPS: HowTo: perform force_empty Michal Hocko
[not found] ` <20150202121520.GB4583-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-02-02 14:08 ` PINTU KUMAR
2015-02-02 14:19 ` 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='002d01d03ece$1971ae10$4c550a30$@samsung.com' \
--to=pintu.k-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=bsingharora-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=cpgs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=xemul-GEFAQzZX7r8dnm+yROfE0A@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.