Re: [Xen-devel] Request for input: Extended event channel support

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

> * What we need to know
> 
> What we're missing in order to make an informed decision is voices
> from the community: If we delay the event channel scalability feature
> until 4.4, how likely is this to be an issue?  Are there current users
> or potential users of Xen who need to be able to scale past 200 VMs on
> a single host, and who would end up choosing another hypervisor if
> this feature were delayed?

For this to work you also need the Linux side patches. That means
that if you want to hit this in v3.10 merge window you have until
April 15th to get it in. The reason is that I am out from
April 20th, and the merge window will probably be open on May 1st.

We need at least one week to work out any bugs when it goes
in #linux-next - hence the April 15th deadline.

Technically sounding, the FIFO looks more appealing than the three
level events, but that is a subjective opinion.

The reality is that what should be really determined is which one
will give better performance. From a design perspective it looks
as FIFO is the clear winner, but perhaps not - I only briefly looked
over the paper?

Anyhow, I am leaning towards the FIFO - but I think that if there are
existing people who want this functionality _Right now_, then
the 3-level event channels would offer a stop-gate option. And they
can apply it to their hypervisor + Linux by hand right?

> 
> Thank you for your time and input.
> 
>  -George Dunlap,
>   4.3 Release manager
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel