From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Luke S Crawford <lsc@prgmr.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: increasing the number of guests (NR_DYNIRQS)
Date: Sat, 20 Feb 2010 13:40:27 +0000 [thread overview]
Message-ID: <C7A596CB.AD03%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <m3pr40tbyd.fsf@luke.xen.prgmr.com>
On 20/02/2010 10:53, "Luke S Crawford" <lsc@prgmr.com> wrote:
> two questions: first, is this stupid? domains appear to be working, and
> I'm currently running north of 200 guests on the server.
>
> second, if this is indeed the right way to fix the problem, if I
> submitted a CONFIG_NR_DYNIRQS patch as Kier suggested in the referenced
> post, would that be considered for acceptance upstream?
Yes, I'd take that for the 2.6.18 tree.
-- Keir
prev parent reply other threads:[~2010-02-20 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 10:53 increasing the number of guests (NR_DYNIRQS) Luke S Crawford
2010-02-20 11:54 ` Tim Post
2010-02-20 13:41 ` Keir Fraser
2010-02-20 15:43 ` Tim Post
2010-02-20 16:41 ` Dan Magenheimer
2010-02-20 13:40 ` Keir Fraser [this message]
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=C7A596CB.AD03%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=lsc@prgmr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).