From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: Implement 3-level event channel routines in Linux.
Date: Thu, 3 Jan 2013 12:12:42 +0000 [thread overview]
Message-ID: <50E575BA.2060305@citrix.com> (raw)
In-Reply-To: <1357214965.18503.11.camel@iceland>
On 03/01/13 12:09, Wei Liu wrote:
>
>>> For both cases, what do you have in mind for the metric that used to
>>> trigger the switch? How much RAM / how many CPUs is the threshold?
>> No idea. At what point are we running out of the events?
> In practice, if you have hundreds or thousands of guests running you're
> likely of running out of event channels. I presume host capable of doing
> this has lots of RAM and CPUs...
>
>
> Wei.
Yes, but the per-cpu stacks are still a fixed size. Xen uses 4 (and a
half-ish) pages. Linux I would guess is similar.
~Andrew
next prev parent reply other threads:[~2013-01-03 12:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 18:38 Implement 3-level event channel routines in Linux Wei Liu
2012-12-31 18:38 ` [RFC PATCH 1/3] Xen: generalized event channel operations Wei Liu
2013-01-02 14:13 ` David Vrabel
2012-12-31 18:38 ` [RFC PATCH 2/3] Xen: rework NR_EVENT_CHANNELS related stuffs Wei Liu
2013-01-02 14:20 ` David Vrabel
2012-12-31 18:38 ` [RFC PATCH 3/3] Xen: implement 3-level event channel routines Wei Liu
2013-01-02 14:57 ` David Vrabel
2013-01-02 18:26 ` Implement 3-level event channel routines in Linux Konrad Rzeszutek Wilk
2013-01-02 18:46 ` Wei Liu
2013-01-02 21:12 ` Konrad Rzeszutek Wilk
2013-01-03 12:09 ` Wei Liu
2013-01-03 12:12 ` Andrew Cooper [this message]
2013-01-04 16:36 ` Konrad Rzeszutek Wilk
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=50E575BA.2060305@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).