From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f200.google.com (mail-pf0-f200.google.com [209.85.192.200]) by kanga.kvack.org (Postfix) with ESMTP id 9E40F6B025F for ; Fri, 15 Jul 2016 09:04:51 -0400 (EDT) Received: by mail-pf0-f200.google.com with SMTP id y134so162616841pfg.1 for ; Fri, 15 Jul 2016 06:04:51 -0700 (PDT) Received: from mail-pa0-x243.google.com (mail-pa0-x243.google.com. [2607:f8b0:400e:c03::243]) by mx.google.com with ESMTPS id d81si4147634pfb.192.2016.07.15.06.04.50 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jul 2016 06:04:50 -0700 (PDT) Received: by mail-pa0-x243.google.com with SMTP id ez1so2676170pab.3 for ; Fri, 15 Jul 2016 06:04:50 -0700 (PDT) Date: Fri, 15 Jul 2016 23:04:58 +1000 From: Balbir Singh Subject: Re: [PATCH 00/14] Present useful limits to user (v2) Message-ID: <20160715130458.GB21685@350D> Reply-To: bsingharora@gmail.com References: <1468578983-28229-1-git-send-email-toiwoton@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1468578983-28229-1-git-send-email-toiwoton@gmail.com> Sender: owner-linux-mm@kvack.org List-ID: To: Topi Miettinen Cc: linux-kernel@vger.kernel.org, Jonathan Corbet , Tony Luck , Fenghua Yu , Alexander Graf , Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , Doug Ledford , Sean Hefty , Hal Rosenstock , Mike Marciniszyn , Dennis Dalessandro , Christian Benvenuti , Dave Goodell , Sudeep Dutt , Ashutosh Dixit , Alex Williamson , Alexander Viro , Tejun Heo , Li Zefan , Johannes Weiner , Peter Zijlstra , Alexei Starovoitov , Arnaldo Carvalho de Melo , Alexander Shishkin , Balbir Singh , Markus Elfring , "David S. Miller" , Nicolas Dichtel , Andrew Morton , Konstantin Khlebnikov , Jiri Slaby , Cyrill Gorcunov , Michal Hocko , Vlastimil Babka , Dave Hansen , Greg Kroah-Hartman , Dan Carpenter , Michael Kerrisk , "Kirill A. Shutemov" , Marcus Gelderie , Vladimir Davydov , Joe Perches , Frederic Weisbecker , Andrea Arcangeli , "Eric W. Biederman" , Andi Kleen , Oleg Nesterov , Stas Sergeev , Amanieu d'Antras , Richard Weinberger , Wang Xiaoqiang , Helge Deller , Mateusz Guzik , Alex Thorlton , Ben Segall , John Stultz , Rik van Riel , Eric B Munson , Alexey Klimov , Chen Gang , Andrey Ryabinin , David Rientjes , Hugh Dickins , Alexander Kuleshov , "open list:DOCUMENTATION" , "open list:IA64 (Itanium) PLATFORM" , "open list:KERNEL VIRTUAL MACHINE (KVM) FOR POWERPC" , "open list:KERNEL VIRTUAL MACHINE (KVM)" , "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)" , "open list:INFINIBAND SUBSYSTEM" , "open list:FILESYSTEMS (VFS and infrastructure)" , "open list:CONTROL GROUP (CGROUP)" , "open list:BPF (Safe dynamic programs and tools)" , "open list:MEMORY MANAGEMENT" On Fri, Jul 15, 2016 at 01:35:47PM +0300, Topi Miettinen wrote: > 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 from the highwater mark values of the resources in question. > I looked where each limit is checked and added a call to update the mark > nearby. > > Example run of program from Documentation/accounting/getdelauys.c: > > ./getdelays -R -p `pidof smartd` > printing resource accounting > RLIMIT_CPU=0 > RLIMIT_FSIZE=0 > RLIMIT_DATA=18198528 > RLIMIT_STACK=135168 > RLIMIT_CORE=0 > RLIMIT_RSS=0 > RLIMIT_NPROC=1 > RLIMIT_NOFILE=55 > RLIMIT_MEMLOCK=0 > RLIMIT_AS=130879488 > RLIMIT_LOCKS=0 > RLIMIT_SIGPENDING=0 > RLIMIT_MSGQUEUE=0 > RLIMIT_NICE=0 > RLIMIT_RTPRIO=0 > RLIMIT_RTTIME=0 > > ./getdelays -R -C /sys/fs/cgroup/systemd/system.slice/smartd.service/ > printing resource accounting > sleeping 1, blocked 0, running 0, stopped 0, uninterruptible 0 > RLIMIT_CPU=0 > RLIMIT_FSIZE=0 > RLIMIT_DATA=18198528 > RLIMIT_STACK=135168 > RLIMIT_CORE=0 > RLIMIT_RSS=0 > RLIMIT_NPROC=1 > RLIMIT_NOFILE=55 > RLIMIT_MEMLOCK=0 > RLIMIT_AS=130879488 > RLIMIT_LOCKS=0 > RLIMIT_SIGPENDING=0 > RLIMIT_MSGQUEUE=0 > RLIMIT_NICE=0 > RLIMIT_RTPRIO=0 > RLIMIT_RTTIME=0 Does this mean that rlimit_data and rlimit_stack should be set to the values as specified by the data above? Do we expect a smart user space daemon to then tweak the RLIMIT values? Balbir Singh. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org