From: Tejun Heo <tj@kernel.org>
To: Krzysztof Opasiak <k.opasiak@samsung.com>
Cc: lizefan@huawei.com, hannes@cmpxchg.org,
"Ł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: Mon, 6 Mar 2017 13:58:20 -0500 [thread overview]
Message-ID: <20170306185820.GA19696@htj.duckdns.org> (raw)
In-Reply-To: <9a57890c-d9e9-5719-e155-ce1161795a02@samsung.com>
Hello,
On Fri, Feb 17, 2017 at 12:37:11PM +0100, Krzysztof Opasiak wrote:
> > 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.
Hmm... I'm not quite sure fds qualify as an independent system-wide
resource. We did that for pids because pids are globally limited and
can run out way earlier than memory backing it. I don't think we have
similar restructions for fds, do we?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-03-06 19:07 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
2017-03-06 18:58 ` Tejun Heo [this message]
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=20170306185820.GA19696@htj.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=k.lewandowsk@samsung.com \
--cc=k.opasiak@samsung.com \
--cc=l.stelmach@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.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
all inboxes | Powered by JetHome®