public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: e8607062@student.tuwien.ac.at,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Elliot Lee <sopwith@redhat.com>
Subject: Re: [PATCH 2.6.13-rc6 1/2] New Syscall: get rlimits of any process (update)
Date: Mon, 22 Aug 2005 22:52:27 -0700	[thread overview]
Message-ID: <a36005b505082222523f81453d@mail.gmail.com> (raw)
In-Reply-To: <1124387342.16072.13.camel@localhost.localdomain>

On 8/18/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Perhaps those application authors should provide a management interface
> to do so within the soft limit range at least. Its not clear to me that
> growing the fd array on a process is even safe. Some programs do size
> arrays at startup after querying the rlimit data.

That's very true.  Using such a remote-rlimit syscall would break all
kinds of code.  It's a basic assumption from Unix/POSIX that the
limits remain constant.  And as Alan hinted at: this is why there are
soft and hard limits.  If tey are set to the same value you obviously
don't get anything.  But this is the application programmer's fault. 
An application which is aware of resources and tries to limit them
should set the soft limits to a reasonable low value and the hard
limit to the absolute maximum (probably the system's maximum).  Then
you can have remote procedure calls into the application to adjust the
soft limits.  Having to change the hard limit means the capacity
planning for the app is completely wrong.  A restart is certainly
acceptable in that case since it should really never happen.

  parent reply	other threads:[~2005-08-23  5:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18  0:57 [PATCH 2.6.13-rc6 1/2] New Syscall: get rlimits of any process (update) Wieland Gmeiner
2005-08-18  1:02 ` [PATCH 2.6.13-rc6 2/2] New Syscall: set " Wieland Gmeiner
2005-08-18  1:57   ` Chris Wright
2005-08-18 15:48   ` Stephen Smalley
2005-08-18  1:17 ` [PATCH 2.6.13-rc6 1/2] New Syscall: get " Chris Wright
2005-08-18  2:05 ` Andi Kleen
2005-08-18 16:19   ` Wieland Gmeiner
2005-08-18 16:40     ` James Morris
2005-08-18 17:49     ` Alan Cox
2005-08-19 17:11       ` Elliot Lee
2005-08-23  5:52       ` Ulrich Drepper [this message]
2005-08-18 18:17     ` Lee Revell
2005-08-18 23:13       ` Alan Cox
2005-08-18 23:16         ` Lee Revell
2005-08-19  0:29           ` Alan Cox
2005-08-19  0:15             ` Lee Revell
2005-08-22  5:15 ` Eric W. Biederman
     [not found] <1124326652.8359.3.camel@w2.suse.lists.linux.kernel>
     [not found] ` <p7364u40zld.fsf@verdi.suse.de.suse.lists.linux.kernel>
     [not found]   ` <1124381951.6251.14.camel@w2.suse.lists.linux.kernel>
2005-08-18 16:39     ` Andi Kleen

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=a36005b505082222523f81453d@mail.gmail.com \
    --to=drepper@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=e8607062@student.tuwien.ac.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sopwith@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