public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wieland Gmeiner <e8607062@student.tuwien.ac.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Elliot Lee <sopwith@redhat.com>
Subject: Re: [PATCH 2.6.13-rc7 2/2] New Syscall: set rlimits of any process (reworked)
Date: Sun, 28 Aug 2005 23:39:58 +0200	[thread overview]
Message-ID: <1125265199.5219.60.camel@w2> (raw)
In-Reply-To: <1125070473.4958.96.camel@localhost.localdomain>

On Fri, 2005-08-26 at 16:34 +0100, Alan Cox wrote:
> On Gwe, 2005-08-26 at 05:39 +0200, Wieland Gmeiner wrote:
> > This is the second of two patches, it implements the setprlimit()
> > syscall.
> > 
> > Implementation: This patch provides a new syscall setprlimit() for
> > writing a given process resource limits for i386. Its implementation
> > follows closely the setrlimit syscall. It is given a pid as an
> 
> 
> While looking at this have you considered 64bit rlimits on a 32bit box.
> If a new API is going to be added it would be a good time to fix the
> fact that some limits should be 64bit nowdays and have 
> 
> setrlimit()		existing legacy/standards API
> setprlimit64()		with size fixed and ability to specify process
> 
> Any thoughts on this ?

Not yet, but thanks for the hint.

Thanks,
Wieland


  reply	other threads:[~2005-08-28 21:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26  3:34 [PATCH 2.6.13-rc7 1/2] New Syscall: get rlimits of any process (reworked) Wieland Gmeiner
2005-08-26  3:39 ` [PATCH 2.6.13-rc7 2/2] New Syscall: set " Wieland Gmeiner
2005-08-26 15:34   ` Alan Cox
2005-08-28 21:39     ` Wieland Gmeiner [this message]
2005-08-31 12:46 ` [PATCH 2.6.13 0/2] New Syscall: get/set rlimits of any process (udate) Wieland Gmeiner
2005-08-31 12:51   ` [PATCH 2.6.13 1/2] " Wieland Gmeiner
2005-08-31 12:52   ` [PATCH 2.6.13 2/2] " Wieland Gmeiner

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=1125265199.5219.60.camel@w2 \
    --to=e8607062@student.tuwien.ac.at \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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