All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher G. Stach II" <cgs@ldsys.net>
To: xen-devel@lists.xensource.com
Subject: Re: kernel Bug after upgrading to 3.0.2-2
Date: Fri, 28 Apr 2006 14:24:14 -0500	[thread overview]
Message-ID: <44526BDE.7020307@ldsys.net> (raw)
In-Reply-To: <a2f23d9322f92953f8cd856f26aaa5f9@cl.cam.ac.uk>

Keir Fraser wrote:
> Each megabyte of emergency pool will allow you to guarantee to be able
> to support 256 processes (counted across all VMs that you are running).
> So the above value would be good for 4096 processes. You'll have to
> decide what you need to set that parameter to.

Is this including LWPs?

-- 
Christopher G. Stach II

  parent reply	other threads:[~2006-04-28 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 16:03 kernel Bug after upgrading to 3.0.2-2 Ian Pratt
2006-04-28 16:06 ` Brian Hays
2006-04-28 16:22   ` Keir Fraser
2006-04-28 16:27     ` Brian Hays
2006-04-28 16:34       ` Keir Fraser
2006-04-28 19:24     ` Christopher G. Stach II [this message]
2006-04-29  7:24       ` Keir Fraser
2006-05-02 15:21     ` Jan Beulich
2006-05-02 16:08       ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2006-04-28 15:58 Brian Hays

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=44526BDE.7020307@ldsys.net \
    --to=cgs@ldsys.net \
    --cc=xen-devel@lists.xensource.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 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.