From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751516AbcGQUE7 (ORCPT ); Sun, 17 Jul 2016 16:04:59 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:35660 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751174AbcGQUEz (ORCPT ); Sun, 17 Jul 2016 16:04:55 -0400 From: Topi Miettinen To: linux-kernel@vger.kernel.org Cc: Topi Miettinen , Tejun Heo , Li Zefan , Johannes Weiner , James Morris , "Serge E. Hallyn" , cgroups@vger.kernel.org (open list:CONTROL GROUP (CGROUP)), linux-security-module@vger.kernel.org (open list:SECURITY SUBSYSTEM) Subject: [PATCH 0/2] help configure some cgroup limits (v2) Date: Sun, 17 Jul 2016 23:03:36 +0300 Message-Id: <1468785820-3960-1-git-send-email-toiwoton@gmail.com> X-Mailer: git-send-email 2.8.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, There are many basic ways to control processes, including capabilities, cgroups and resource limits. However, there are far fewer ways to find out useful values for the limits, except blind trial and error. This patch series attempts to fix that by giving at least a nice starting point for configuration of PID and device cgroups. Thanks to the commenters for the previous version. -Topi Topi Miettinen (2): cgroup_pids: track highwater mark of pids device_cgroup: track and present accessed devices kernel/cgroup_pids.c | 51 ++++++++++++++++++++++++++-- security/device_cgroup.c | 86 ++++++++++++++++++++++++++++++++++++++---------- 2 files changed, 117 insertions(+), 20 deletions(-) -- 2.8.1