From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: grendel@caudium.net
Cc: Peter Chubb <peter@chubb.wattle.id.au>,
Jeff Dike <jdike@addtoit.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: user- vs kernel-level resource sandbox for Linux?
Date: Tue, 30 Nov 2004 18:48:27 +0000 [thread overview]
Message-ID: <1101840505.25628.105.camel@localhost.localdomain> (raw)
In-Reply-To: <20041130023947.GI5378@beowulf.thanes.org>
On Maw, 2004-11-30 at 02:39, Marek Habersack wrote:
> 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...
I'd suggest playing with Xen - its very efficient and it really does
come close to perfect constraint for resources.
next prev parent reply other threads:[~2004-11-30 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 10:19 Marek Habersack
2004-11-29 20:00 ` Jeff Dike
2004-11-29 22:13 ` Peter Chubb
2004-11-30 2:39 ` Marek Habersack
2004-11-30 18:48 ` Alan Cox [this message]
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=1101840505.25628.105.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome