All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: KPATCH] Reserve VM for root (was: Re: Looking for better VM)
Date: Thu, 16 Nov 2000 17:03:54 +0100	[thread overview]
Message-ID: <20001116170354.A9501@caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0011161513480.20626-100000@fs129-190.f-secure.com> <Pine.LNX.4.21.0011161313310.13085-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0011161313310.13085-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Thu, Nov 16, 2000 at 01:51:01PM -0200

On Thu, Nov 16, 2000 at 01:51:01PM -0200, Rik van Riel wrote:
> > If you think fork() kills the box then ulimit the maximum number
> > of user processes (ulimit -u). This is a different issue and a
> > bad design in the scheduler (see e.g. Tru64 for a better one).
> 
> My fair scheduler catches this one just fine. It hasn't
> been integrated in the kernel yet, but both VA Linux and
> Conectiva use it in their kernel RPM.

BTW: do you have a fairsched patch for 2.4?

	Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@ns.caldera.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: KPATCH] Reserve VM for root (was: Re: Looking for better VM)
Date: Thu, 16 Nov 2000 17:03:54 +0100	[thread overview]
Message-ID: <20001116170354.A9501@caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0011161313310.13085-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Thu, Nov 16, 2000 at 01:51:01PM -0200

On Thu, Nov 16, 2000 at 01:51:01PM -0200, Rik van Riel wrote:
> > If you think fork() kills the box then ulimit the maximum number
> > of user processes (ulimit -u). This is a different issue and a
> > bad design in the scheduler (see e.g. Tru64 for a better one).
> 
> My fair scheduler catches this one just fine. It hasn't
> been integrated in the kernel yet, but both VA Linux and
> Conectiva use it in their kernel RPM.

BTW: do you have a fairsched patch for 2.4?

	Christoph

-- 
Always remember that you are unique.  Just like everyone else.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-11-16 16:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-02  6:21 KPATCH] Reserve VM for root (was: Re: Looking for better VM) pavel-velo
1997-01-02  6:21 ` pavel-velo
2000-11-16 15:01 ` Szabolcs Szakacsits
2000-11-16 15:01   ` Szabolcs Szakacsits
2000-11-16 15:51   ` Rik van Riel
2000-11-16 15:51     ` Rik van Riel
2000-11-16 16:03     ` Christoph Hellwig [this message]
2000-11-16 16:03       ` Christoph Hellwig
2000-11-16 16:05       ` Rik van Riel
2000-11-16 16:05         ` Rik van Riel
2000-11-16 21:33     ` Szabolcs Szakacsits
2000-11-16 21:33       ` Szabolcs Szakacsits
2000-11-18 20:49   ` Pavel Machek
2000-11-18 20:49     ` Pavel Machek

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=20001116170354.A9501@caldera.de \
    --to=hch@ns.caldera.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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.