From: J Sloan <jjs@pobox.com>
To: dmaynor@iceland.oit.gatech.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.8 Resource leaks + limits
Date: Tue, 14 Aug 2001 22:56:17 -0700 [thread overview]
Message-ID: <3B7A0F01.DC4CAE4@pobox.com> (raw)
In-Reply-To: <3ce801c12548$b7971750$020a0a0a@totalmef> <200108150532.f7F5WGq01653@penguin.transmeta.com> <20010815014328.A15395@iceland.oit.gatech.edu>
dmaynor@iceland.oit.gatech.edu wrote:
> > This is why you mainly find per-process stuff in all the limits.
> >
> > Linux has had (for a while now) a "struct user" that is actually quickly
> > accessible through a direct pointer off every process that is associated
> > with that user, and we could (and _will_) start adding these kinds of
> > limits. However, part of the problem is that because the limits haven't
> > historically existed, there is also no accepted and nice way of setting
> > the limits.
> So when you do impose this, where will it be setable, will there be a flat file in /etc
> like solaris, or compile time for the kernel?
Eh?
Why wouldn't it be like most parameters in Linux,
e.g. dynamically adjustable via a sysctl or /proc?
IMHO, of course...
cu
jjs
next prev parent reply other threads:[~2001-08-15 5:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 5:11 2.4.8 Resource leaks + limits Magnus Naeslund(f)
2001-08-15 5:32 ` Linus Torvalds
2001-08-15 5:42 ` Ulrich Drepper
2001-08-15 8:31 ` Nadav Har'El
2001-08-15 5:43 ` dmaynor
2001-08-15 5:56 ` J Sloan [this message]
2001-08-15 6:59 ` Brian
2001-08-15 7:26 ` J Sloan
2001-08-15 13:51 ` Admin Mailing Lists
2001-08-15 14:12 ` dmaynor
2001-08-15 16:04 ` Alan Cox
2001-08-17 22:01 ` Rik van Riel
2001-08-17 22:08 ` Alan Cox
2001-08-17 23:25 ` Rik van Riel
2001-08-15 6:05 ` Magnus Naeslund(f)
2001-08-15 6:28 ` Alexander Viro
2001-08-15 7:24 ` Magnus Naeslund(f)
2001-08-15 14:21 ` Szabolcs Szakacsits
2001-08-15 14:20 ` Magnus Naeslund(f)
2001-08-16 19:41 ` Szabolcs Szakacsits
2001-08-16 19:54 ` Szabolcs Szakacsits
2001-08-17 15:56 ` Magnus Naeslund(f)
2001-08-15 15:00 ` Tobias Ringstrom
[not found] <no.id>
2001-08-15 11:40 ` Alan Cox
2001-08-15 16:53 ` Linus Torvalds
2001-08-15 18:51 ` Alan Cox
2001-08-15 19:57 ` Ingo Oeser
2001-08-15 20:15 ` Alan Cox
2001-08-15 21:30 ` Jesse Pollard
2001-08-15 20:57 ` Anton Altaparmakov
2001-08-16 1:12 ` Jesse Pollard
2001-08-15 22:14 ` Horst von Brand
[not found] <Pine.LNX.4.33L.0108171818040.2277-100000@duckman.distro.conectiva>
2001-08-18 14:53 ` Magnus Naeslund(f)
2001-08-18 15:24 ` Szabolcs Szakacsits
2001-08-18 15:20 ` Rik van Riel
2001-08-18 22:34 ` Alan Cox
2001-08-18 22:35 ` Alan Cox
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=3B7A0F01.DC4CAE4@pobox.com \
--to=jjs@pobox.com \
--cc=dmaynor@iceland.oit.gatech.edu \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.