From: Marek Habersack <grendel@caudium.net>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Jeff Dike <jdike@addtoit.com>, linux-kernel@vger.kernel.org
Subject: Re: user- vs kernel-level resource sandbox for Linux?
Date: Tue, 30 Nov 2004 03:39:47 +0100 [thread overview]
Message-ID: <20041130023947.GI5378@beowulf.thanes.org> (raw)
In-Reply-To: <16811.40687.892939.304185@wombat.chubb.wattle.id.au>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
On Tue, Nov 30, 2004 at 09:13:03AM +1100, Peter Chubb scribbled:
> >>>>> "Jeff" == Jeff Dike <jdike@addtoit.com> writes:
>
> Jeff> grendel@caudium.net said:
> >> I would appreciate any pointers to the userland solutions for that
> >> problem (if any exist) before I resort to Xen/UML.
>
> Jeff> UML would be exactly what you're looking for.
>
> Jeff> Jeff
>
> apart from the performance hit :-(
that's the problem...
>
> There have been a number of different approaches proposed in the past
> to limit real memory usage per-process; search for RSS limit in the
> archives.
per-process isn't enough. I specifically need something to limit the memory
usage on a more global scale - per user ID or per process group or a similar
way of grouping related processes. That's the only way to tame processes
like apache. At this point the option I'm considering is Xen, unless I can
find a userland solution to the problem...
regards,
marek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-30 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 10:19 user- vs kernel-level resource sandbox for Linux? Marek Habersack
2004-11-29 20:00 ` Jeff Dike
2004-11-29 22:13 ` Peter Chubb
2004-11-30 2:39 ` Marek Habersack [this message]
2004-11-30 18:48 ` Alan Cox
2004-11-30 20:47 ` Marek Habersack
2004-11-30 20:20 ` Alan Cox
2004-12-02 2:32 ` Herbert Poetzl
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=20041130023947.GI5378@beowulf.thanes.org \
--to=grendel@caudium.net \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
/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.