From: Krzysztof Opasiak <k.opasiak@samsung.com>
To: tj@kernel.org, lizefan@huawei.com, hannes@cmpxchg.org
Cc: "Łukasz Stelmach" <l.stelmach@samsung.com>,
linux-kernel@vger.kernel.org,
"Karol Lewandowski" <k.lewandowsk@samsung.com>,
cgroups@vger.kernel.org
Subject: Re: counting file descriptors with a cgroup controller
Date: Fri, 17 Feb 2017 12:37:11 +0100 [thread overview]
Message-ID: <9a57890c-d9e9-5719-e155-ce1161795a02@samsung.com> (raw)
In-Reply-To: <87poihtaya.fsf%l.stelmach@samsung.com>
+ cgroups mailing list
+ cgroup maintainers
On 02/17/2017 10:37 AM, Łukasz Stelmach wrote:
> Hi,
>
> We need to limit and monitor the number of file descriptors processes
> keep open. If a process exceeds certain limit we'd like to terminate it
> and restart it or reboot the whole system. Currently the RLIMIT API
> allows limiting the number of file descriptors but to achieve our goals
> we'd need to make sure all programmes we run handle EMFILE errno
> properly. That is why we consider developing a cgroup controller that
> limits the number of open file descriptors of its members (similar to
> memory controler).
>
> Any comments? Is there any alternative that:
>
> + does not require modifications of user-land code,
> + enables other process (e.g. init) to be notified and apply policy.
>
> Kind regards,
>
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2017-02-17 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170217093725eucas1p12478baf297d25303f3020f4973fbf3b0@eucas1p1.samsung.com>
2017-02-17 9:37 ` Łukasz Stelmach
2017-02-17 11:37 ` Krzysztof Opasiak [this message]
2017-03-06 18:58 ` Tejun Heo
2017-03-07 11:19 ` Krzysztof Opasiak
2017-03-07 19:41 ` Tejun Heo
2017-03-07 20:06 ` Krzysztof Opasiak
2017-03-07 20:48 ` Tejun Heo
2017-03-08 2:59 ` Parav Pandit
2017-03-08 10:19 ` Krzysztof Opasiak
2017-03-08 9:52 ` Krzysztof Opasiak
2017-03-08 18:59 ` Tejun Heo
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=9a57890c-d9e9-5719-e155-ce1161795a02@samsung.com \
--to=k.opasiak@samsung.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=k.lewandowsk@samsung.com \
--cc=l.stelmach@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®