Return-Path: <linux-kernel-owner+w=401wt.eu-S932842AbZJ3SYg@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932842AbZJ3SYg (ORCPT <rfc822;w@1wt.eu>);
	Fri, 30 Oct 2009 14:24:36 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932822AbZJ3SYf
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 30 Oct 2009 14:24:35 -0400
Received: from charlotte.tuxdriver.com ([70.61.120.58]:59678 "EHLO
	smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932802AbZJ3SYe (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 30 Oct 2009 14:24:34 -0400
Date: Fri, 30 Oct 2009 14:24:28 -0400
From: Neil Horman <nhorman@tuxdriver.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, marcin.slusarz@gmail.com, tglx@linutronix.de,
       mingo@redhat.com, hpa@zytor.com
Subject: Re: [PATCH 0/3] extend get/setrlimit to support setting rlimits
	external to a process (v7)
Message-ID: <20091030182428.GB5181@hmsreliant.think-freely.org>
References: <20090928200600.GA3053@hmsreliant.think-freely.org> <20091001171538.GB2456@hmsreliant.think-freely.org> <20091012161342.GA32088@hmsreliant.think-freely.org> <20091012201304.GG32088@hmsreliant.think-freely.org> <20091020005214.GA8886@localhost.localdomain> <20091028144426.GA7422@hmsreliant.think-freely.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091028144426.GA7422@hmsreliant.think-freely.org>
User-Agent: Mutt/1.5.19 (2009-01-05)
X-Spam-Score: -4.1 (----)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2019
Lines: 46

On Wed, Oct 28, 2009 at 10:44:26AM -0400, Neil Horman wrote:
> On Mon, Oct 19, 2009 at 08:52:15PM -0400, Neil Horman wrote:
> > Ok, I give.  I was hoping that some of the requestors of this feature would pipe
> > up and support the use case for the proc file interface to set limits.  clearly
> > they're not that interested, but I still think theres merit in the patch.  So
> > heres version 7 of this patch set.  Its the same as before, but the proc
> > interface has been dropped, leaving only the syscall interface behind.  I've
> > tested the interface on intel 32 and 64 bit, with success
> > 
> > Summary:
> > 
> > Its been requested often that we have the ability to read and modify process
> > rlimit values from contexts external to the owning process.  Ideally this allows
> > sysadmins to adjust rlimits on long running processes wihout the need to stop
> > and restart those processes, which incurs undesireable downtime.  This patch
> > enables that functionality,  It does so in two places.  First it enables process
> > limit setting by writing to the /proc/pid/limits file a string in the format:
> > <limit> <current limit> <max limit> > /proc/<pid>/limits
> > where limit is one of
> > [as,core,cpu,data,fsize,locks,memlock,msgqueue,nice,nofile,nproc,rss,rtprio,rttime]
> > 
> > Secondly it allows for programatic setting of these limits via 2 new syscalls,
> > getprlimit, and setprlimit, which act in an identical fashion to getrlimit and
> > setrlimit respectively, except that they except a process id as an extra
> > argument, to specify the process id of the rlimit values that you wish to
> > read/write
> > 
> > Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> >  
> >  
> >  
> >  
> > 
> 
> Ping?  Any thoughts
> Regards
> Neil

Ping?
Neil

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/