From: Krzysztof Opasiak <k.opasiak@samsung.com>
To: Parav Pandit <pandit.parav@gmail.com>, Tejun Heo <tj@kernel.org>
Cc: "Li Zefan" <lizefan@huawei.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Łukasz Stelmach" <l.stelmach@samsung.com>,
"Linux Kernel Mailing List" <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: Wed, 08 Mar 2017 11:19:31 +0100 [thread overview]
Message-ID: <607306a7-c075-b2e0-777d-d5a4c790527e@samsung.com> (raw)
In-Reply-To: <CAG53R5VQrm-c-F8GdqJ9fx4n+=QU5n3gT-9adx4HqRO_R8BOaw@mail.gmail.com>
On 03/08/2017 03:59 AM, Parav Pandit wrote:
> Hi,
>
> On Tue, Mar 7, 2017 at 2:48 PM, Tejun Heo <tj@kernel.org> wrote:
>>
>> Hello,
>>
>> On Tue, Mar 07, 2017 at 09:06:49PM +0100, Krzysztof Opasiak wrote:
>>> Personally, I don't want to use rlimit for this as it ends up returning
>>> error code from for example open() when we hit the limit. This may lead to
>>> some unpredictable crashes in services (esp. those poor proprietary binary
>>> blobs). Instead of injecting errors to service we would like to just get
>>> notification that this service has more opened fds than it should and ask it
>>> to restart in a polite way.
>>>
>
> How does those poor proprietary binary blobs remain polite after restart?
They wont.
> Do you mean you want to keep restarting them when it reaches the limit?
We'd like to restart them each time when they reach limit declared by
developer.
Best regards,
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2017-03-08 10:22 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
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 [this message]
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=607306a7-c075-b2e0-777d-d5a4c790527e@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=pandit.parav@gmail.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®