Date: Wed, 23 Feb 2005 19:06:43 -0800
From: Chris Wright <chrisw@osdl.org>
To: Roland McGrath <roland@redhat.com>
Cc: Chris Wright <chrisw@osdl.org>, Jeremy Fitzhardinge <jeremy@goop.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] show RLIMIT_SIGPENDING usage in /proc/PID/status
Message-ID: <20050224030643.GB28536@shell0.pdx.osdl.net>
References: <20050224023349.GF15867@shell0.pdx.osdl.net> <200502240255.j1O2tj8M010857@magilla.sf.frob.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200502240255.j1O2tj8M010857@magilla.sf.frob.com>
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1223
Lines: 30

* Roland McGrath (roland@redhat.com) wrote:
> > Two questions: 1) This changes the interface for consumers of
> > /proc/[pid]/status data, do we care?  Adding new line like this should be
> > safe enough.
> 
> As far as I can tell, noone fretted about the addition of Threads:,
> ShdPnd:, etc., which were not always there.

Sounds good ;-)

> > 2) Perhaps we should do /proc/[pid]/rlimit/ type dir for each value?
> >    This has been asked for before.
> 
> Is the request to see the limit settings, or the current usage, or both?
> What kind of format are you suggesting?  I don't see a need for something
> with a million little files.  Also, for some of the limits the correct
> current usage count is not trivial to ascertain.  (And for others like
> RLIMIT_FSIZE and RLIMIT_CORE, it is of course not meaningful at all.)

Probably just one file per rlimit with usage, cur, max.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net
-
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/