From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752253AbcFXC4Q (ORCPT ); Thu, 23 Jun 2016 22:56:16 -0400 Received: from mx2.suse.de ([195.135.220.15]:43118 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751905AbcFXC4P (ORCPT ); Thu, 23 Jun 2016 22:56:15 -0400 From: Aleksa Sarai To: Jonathan Corbet , Tejun Heo , Li Zefan , Johannes Weiner , Kenny Yu Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, Aleksa Sarai Subject: [PATCH 0/2] cgroup: pids: extend pids.events Date: Fri, 24 Jun 2016 13:00:47 +1000 Message-Id: <20160624030049.13341-1-asarai@suse.de> X-Mailer: git-send-email 2.8.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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