From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Roger Heflin <rheflin@atipa.com>
Cc: "'Al Boldi'" <a1426z@gawab.com>, linux-kernel@vger.kernel.org
Subject: RE: Resource limits
Date: Mon, 26 Sep 2005 18:11:30 +0100 [thread overview]
Message-ID: <1127754691.27757.26.camel@localhost.localdomain> (raw)
In-Reply-To: <EXCHG2003ogxLDp7mvj00000ae4@EXCHG2003.microtech-ks.com>
On Llu, 2005-09-26 at 09:44 -0500, Roger Heflin wrote:
> While talking about limits, one of my customers report that if
> they set "ulimit -d" to be say 8GB, and then a program goes and
The kernel doesn't yet support rlimit64() - glibc does but it emulates
it best effort. Thats a good intro project for someone
> It would seem that the best thing to do would be to abort on
> allocates that will by themselves exceed the limit.
2.6 supports "no overcommit" modes.
Alan
next prev parent reply other threads:[~2005-09-26 16:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 14:12 Resource limits Al Boldi
2005-09-26 3:36 ` Rik van Riel
2005-09-26 14:18 ` Al Boldi
2005-09-26 15:56 ` Neil Horman
2005-09-26 17:32 ` Al Boldi
2005-09-26 17:51 ` Neil Horman
2005-09-26 20:26 ` Al Boldi
2005-09-27 1:05 ` Neil Horman
2005-09-27 5:08 ` Al Boldi
2005-09-27 12:08 ` Neil Horman
2005-09-27 13:42 ` Al Boldi
2005-09-27 14:36 ` Neil Horman
2005-09-27 15:50 ` Al Boldi
2005-09-27 17:25 ` Neil Horman
2005-09-27 21:35 ` Chandra Seetharaman
2005-09-26 12:28 ` Neil Horman
2005-09-26 14:44 ` Roger Heflin
2005-09-26 17:11 ` Alan Cox [this message]
2005-09-26 17:32 ` Al Boldi
2005-09-26 21:21 ` Roger Heflin
2005-09-27 3:50 ` Coywolf Qi Hunt
2005-09-26 19:07 ` Matthew Helsley
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 12:13 Frank Cornelis
2002-10-24 16:46 ` Randolph Bentson
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=1127754691.27757.26.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rheflin@atipa.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