From: Wei Liu <Wei.Liu2@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: wei.liu2@citrix.com, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Implement 3-level event channel routines in Linux.
Date: Thu, 3 Jan 2013 12:09:25 +0000 [thread overview]
Message-ID: <1357214965.18503.11.camel@iceland> (raw)
In-Reply-To: <20130102211203.GA15122@phenom.dumpdata.com>
On Wed, 2013-01-02 at 21:12 +0000, Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 02, 2013 at 06:46:58PM +0000, Wei Liu wrote:
> > On Wed, 2013-01-02 at 18:26 +0000, Konrad Rzeszutek Wilk wrote:
> > > On Mon, Dec 31, 2012 at 06:38:54PM +0000, Wei Liu wrote:
> > > > This patch series implements 3-level event channel routines in Linux kernel.
> > > >
> > > > My thought is that 3-level event channel is only useful for Dom0 or driver
> > > > domain, so it is not enabled by default. Enable it with evtchn_level=3 in
> > > > kernel command line.
> > >
> > > Could it be enabled dynamically? Say when we are close to exhausting the
> > > amount of channels? Or if the machine has some large amount of memory and
> > > hence would probably allocate many many guests?
> > >
> >
> > Do you mean enabling this mechanism on the fly when Dom0 / driver domain
> > is running? Or do you mean enabling it based on some metrics when
> > starting up a domain?
>
> Either one.
> >
> > If it is the first case, who is responsible for initiating the switching
> > process? It looks like it is Xen's responsibility to do the switch
> > because Dom0 sometimes cannot know the true capability of underlying
> > hardware. If it is Xen, then we need to add callback to poke Dom0 /
> > driver domain.
>
> Huh? It would be as simple as Dom0 just figuring out that it is
> at the end of the available events (b/c its close to the MAX) and
> then transitioning to the 3-level one (if it can).
>
We need to manipulate various data structures. IMHO this makes
implementation tricky and racy.
> >
> > 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.
next prev parent reply other threads:[~2013-01-03 12:09 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 [this message]
2013-01-03 12:12 ` Andrew Cooper
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=1357214965.18503.11.camel@iceland \
--to=wei.liu2@citrix.com \
--cc=konrad.wilk@oracle.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).