mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Wed, 23 Feb 2005 19:06:43 -0800	[thread overview]
Message-ID: <20050224030643.GB28536@shell0.pdx.osdl.net> (raw)
In-Reply-To: <200502240255.j1O2tj8M010857@magilla.sf.frob.com>

* 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

  reply	other threads:[~2005-02-24  3:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23  6:42 [PATCH] Always send siginfo for synchronous signals Jeremy Fitzhardinge
2005-02-23 20:19 ` Chris Wright
2005-02-23 23:09   ` Jeremy Fitzhardinge
2005-02-23 23:46     ` Chris Wright
2005-02-24  0:50       ` Jeremy Fitzhardinge
2005-02-24  2:07     ` [PATCH] show RLIMIT_SIGPENDING usage in /proc/PID/status Roland McGrath
2005-02-24  2:33       ` Chris Wright
2005-02-24  2:55         ` Roland McGrath
2005-02-24  3:06           ` Chris Wright [this message]
2005-02-24  2:24     ` [PATCH] set RLIMIT_SIGPENDING limit based on RLIMIT_NPROC Roland McGrath
2005-02-24  3:07       ` Chris Wright
2005-02-25  2:05         ` Jeremy Fitzhardinge
2005-02-25  2:10           ` Chris Wright
2005-02-23 23:44   ` [PATCH] Always send siginfo for synchronous signals Jeremy Fitzhardinge
2005-02-24  1:45     ` [PATCH] override RLIMIT_SIGPENDING for non-RT signals Roland McGrath
2005-02-24  2:32       ` Chris Wright
2005-02-24  2:43         ` Roland McGrath
2005-02-24  3:12           ` Chris Wright
2005-02-25  2:01       ` Jeremy Fitzhardinge
2005-02-25  2:12         ` Chris Wright
2005-02-25  2:16           ` Roland McGrath
2005-02-25  3:02             ` Chris Wright

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050224030643.GB28536@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=akpm@osdl.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®