Linux cgroups development
 help / color / mirror / Atom feed
From: Aleksa Sarai <asarai@suse.de>
To: Jonathan Corbet <corbet@lwn.net>, Tejun Heo <tj@kernel.org>,
	Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>, Kenny Yu <kennyyu@fb.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	cgroups@vger.kernel.org, Aleksa Sarai <asarai@suse.de>
Subject: [PATCH 0/2] cgroup: pids: extend pids.events
Date: Fri, 24 Jun 2016 13:00:47 +1000	[thread overview]
Message-ID: <20160624030049.13341-1-asarai@suse.de> (raw)

While reading the patchset by Kenny Yu, I realised that not having a
field for the "recent" number of failed forks means that userspace would
have trouble accurately deciding whether or not it should increase the
limits.

In addition, by having hits_since, we get to maintain the
on-reset-we-log-failures-again semantics that Tejun said he liked.

Aleksa Sarai (2):
  cgroup: pids: show number of failed forks since limit reset
  docs: cgroup/pids: update documentation to include pids.events

 Documentation/cgroup-v1/pids.txt | 18 ++++++++++++++++++
 kernel/cgroup_pids.c             | 31 ++++++++++++++++++++++---------
 2 files changed, 40 insertions(+), 9 deletions(-)

-- 
2.8.4


             reply	other threads:[~2016-06-24  3:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24  3:00 Aleksa Sarai [this message]
2016-06-24  3:00 ` [PATCH 1/2] cgroup: pids: show number of failed forks since limit reset Aleksa Sarai
2016-06-24  3:00   ` [PATCH 2/2] docs: cgroup/pids: update documentation to include pids.events Aleksa Sarai
2016-06-24 15:31   ` [PATCH 1/2] cgroup: pids: show number of failed forks since limit reset Tejun Heo
     [not found]     ` <20160624153151.GQ3262-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2016-06-26 11:34       ` Aleksa Sarai
2016-06-26 23:42         ` Tejun Heo
2016-06-29  5:10           ` Aleksa Sarai
     [not found]             ` <ec289e47-9761-ff21-b264-1391aa22cfd4-l3A5Bk7waGM@public.gmane.org>
2016-06-29 15:33               ` 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=20160624030049.13341-1-asarai@suse.de \
    --to=asarai@suse.de \
    --cc=cgroups@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=hannes@cmpxchg.org \
    --cc=kennyyu@fb.com \
    --cc=linux-doc@vger.kernel.org \
    --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