From: Aleksa Sarai <asarai@suse.de>
To: Ivan Zahariev <famzah@icdsoft.com>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Cgroups "pids" controller does not update "pids.current" count immediately
Date: Fri, 15 Jun 2018 03:26:34 +1000 [thread overview]
Message-ID: <20180614172634.ymoik5uov3vzftmp@gordon> (raw)
In-Reply-To: <77af3805-e912-2664-f347-e30c0919d0c4@icdsoft.com>
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
On 2018-06-14, Ivan Zahariev <famzah@icdsoft.com> wrote:
> I posted a kernel bug about this a month ago but it did not receive any
> attention: https://bugzilla.kernel.org/show_bug.cgi?id=199713
I believe that very few people watch the kernel bugzilla -- it's almost
always better to send a mail to LKML (speaking of which, you should
always include <linux-kernel@vger.kernel.org> in Cc).
> I've tested this on 4.14.27 and 4.4.0-124-generic Ubuntu.
>
> If I start a couple of processes which exit very quickly (like a simple Bash
> script with many commands in it), the reported value in "pids.current" is
> not updated immediately when processes exit. This leads to too many
> processes incorrectly accounted in "pids.current" which hits the "pids.max"
> prematurely.
One possible reason for this might be related to zombie processes.
cgroup.procs doesn't include any zombie processes (tasks are removed
when they exit(2)), but the pids controller does track zombies (tasks
are removed when the 'struct task' is put'd). This could explain why
there's a discrepancy which clears itself up after a short period of
time -- though I am not sure that your reproducer will actually produce
zombies (I only took a quick look at it).
> The "memory" controller, for example, works as expected and does not suffer
> from this asynchronous lag.
I'm not sure what makes the memory controller and the pids controller
comparable in this aspect -- there is no "pids.current" for the memory
controller.
--
Aleksa Sarai
Senior Software Engineer (Containers)
SUSE Linux GmbH
<https://www.cyphar.com/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2018-06-14 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <77af3805-e912-2664-f347-e30c0919d0c4@icdsoft.com>
2018-06-14 17:26 ` Aleksa Sarai [this message]
2018-06-14 17:27 ` Aleksa Sarai
[not found] ` <20180614150650.GU1351649@devbig577.frc2.facebook.com>
2018-06-15 14:26 ` Ivan Zahariev
2018-06-15 15:41 ` Tejun Heo
2018-06-15 16:07 ` Ivan Zahariev
2018-06-15 16:16 ` Tejun Heo
2018-06-15 17:40 ` Ivan Zahariev
2018-06-15 19:07 ` Tejun Heo
2018-06-15 19:38 ` Ivan Zahariev
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=20180614172634.ymoik5uov3vzftmp@gordon \
--to=asarai@suse.de \
--cc=cgroups@vger.kernel.org \
--cc=famzah@icdsoft.com \
--cc=linux-kernel@vger.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®