From: Keir Fraser <keir@xensource.com>
To: "Carb, Brian A" <Brian.Carb@unisys.com>,
Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com, "Puthiyaparambil,
Aravindh" <aravindh.puthiyaparambil@unisys.com>,
Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: Maximum number of domains and NR_IRQS
Date: Fri, 08 Dec 2006 06:32:13 +0000 [thread overview]
Message-ID: <C19EB76D.586E%keir@xensource.com> (raw)
In-Reply-To: <B05D2E415E8CC94897BB44233D14EE6804EB48B7@USTR-EXCH5.na.uis.unisys.com>
On 7/12/06 8:55 pm, "Carb, Brian A" <Brian.Carb@unisys.com> wrote:
> Thanks Keir - We changed NR_DYNIRQS to 768 and we were successfully able
> to bring up 200 VMs.
> Can we submit a patch to increase NR_DYNIRQS to 1024?
>
>
> brian carb - unisys corporation - malvern, pa
We'd take a CONFIG_NR_DYNIRQS patch (i.e., integrate with Kconfig). We'd
also love a patch that would make the IRQ space dynamically growable
(although I'm not sure how much impact this might have on non-xen-specific
irq code). Also potentially useful and easier to implement would be to make
the NR_DYN_IRQS selectable at boot time (i.e., via a boot parameter, or bump
it when the guest realises it is domain 0). But we don't want to change the
default for everyone all the time -- the current value is good for just
about everyone, and growing it just wastes space for most people.
-- Keir
next prev parent reply other threads:[~2006-12-08 6:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 15:37 Maximum number of domains and NR_IRQS Carb, Brian A
2006-12-07 15:50 ` Keir Fraser
2006-12-07 16:08 ` Carb, Brian A
2006-12-07 16:14 ` Ian Campbell
2006-12-07 16:25 ` Keir Fraser
2006-12-07 16:42 ` Puthiyaparambil, Aravindh
2006-12-07 16:47 ` Keir Fraser
2006-12-07 20:55 ` Carb, Brian A
2006-12-08 6:32 ` Keir Fraser [this message]
2006-12-11 21:06 ` Carb, Brian A
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=C19EB76D.586E%keir@xensource.com \
--to=keir@xensource.com \
--cc=Brian.Carb@unisys.com \
--cc=Ian.Campbell@XenSource.com \
--cc=aravindh.puthiyaparambil@unisys.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 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.