From: "Zhao Hui Ding" <dingzhh@cn.ibm.com>
To: linux-mm@kvack.org
Subject: memory.force_empty is deprecated
Date: Fri, 4 Nov 2016 16:24:25 +0800 [thread overview]
Message-ID: <OF57AEC2D2.FA566D70-ON48258061.002C144F-48258061.002E2E50@notes.na.collabserv.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
Hello,
I'm Zhaohui from IBM Spectrum LSF development team. I got below message
when running LSF on SUSE11.4, so I would like to share our use scenario
and ask for the suggestions without using memory.force_empty.
memory.force_empty is deprecated and will be removed. Let us know if it is
needed in your usecase at linux-mm@kvack.org
LSF is a batch workload scheduler, it uses cgroup to do batch jobs
resource enforcement and accounting. For each job, LSF creates a cgroup
directory and put job's PIDs to the cgroup.
When we implement LSF cgroup integration, we found creating a new cgroup
is much slower than renaming an existing cgroup, it's about hundreds of
milliseconds vs less than 10 milliseconds.
To speed up job clean up, when a job is done, LSF doesn't delete the
cgroup, instead, LSF reset the memory usage by setting memory.force_empty
to "0". The subsequent job will rename the cgroup name and reuse it.
If memory.force_empty will be removed, how to achieve the same goal?
Looking forward for you reply.
Thanks & Regards,
Zhaohui Ding (丁肇辉), Ph.D
Senior Product Architect, IBM Platform LSF Product Line
IBM China Systems and Technology Laboratory in Beijing
Addr: Building 28, ZhongGuanCun Software Park, No.8 Dong Bei Wang West
Road
Office : (86-10) 82450903 Mobile : (86) 186-1198-2179
[-- Attachment #2: Type: text/html, Size: 1934 bytes --]
next reply other threads:[~2016-11-04 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 8:24 Zhao Hui Ding [this message]
2016-11-04 15:21 ` Johannes Weiner
2016-11-17 10:13 ` Zhao Hui Ding
2016-11-22 15:20 ` Michal Hocko
2016-11-17 10:39 ` Balbir Singh
2016-11-18 6:28 ` Zhao Hui Ding
2016-11-18 22:08 ` Balbir Singh
2016-11-22 15:21 ` 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=OF57AEC2D2.FA566D70-ON48258061.002C144F-48258061.002E2E50@notes.na.collabserv.com \
--to=dingzhh@cn.ibm.com \
--cc=linux-mm@kvack.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