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: Tue, 7 Mar 2017 14:41:34 -0500 [thread overview]
Message-ID: <20170307194134.GE31179@htj.duckdns.org> (raw)
In-Reply-To: <7fbd9c4c-76ca-4073-9afa-1ab54364ec79@samsung.com>
Hello, Krzysztof.
On Tue, Mar 07, 2017 at 12:19:52PM +0100, Krzysztof Opasiak wrote:
> So maybe let me clarify our use case so we can have some more discussion
> about this. We are dealing with task of monitoring system services on an IoT
> system. So this system needs to run as long as possible without reboot just
> like server. In server world almost whole system state is being monitored by
> services like nagios. They measure each parameter (like cpu, memory etc)
> with some interval. Unfortunately we cannot use this it in an embedded
> system due to power consumption.
So, we don't add controllers for specific use case scenarios. The
target actually has to be a fundamental resource which can't be
isolated in a different way.
The use case you're describing is more about working around
shortcomings in userspace by implemneting a major kernel feature, when
the said shortcomings can easily be controlled and mitigated from
userspace - e.g. if running out of fds can't be handled reliably from
the target application for some reason and the application may lock up
from the condition, protect the base resources so that a monitoring
process can always reliably run and let that take a corrective action
when such condition is detected.
This doesn't really seem to qualify as a dedicated kernel
functionality.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-03-07 19:42 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 [this message]
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=20170307194134.GE31179@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®