From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
George Dunlap <dunlapg@umich.edu>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Request for input: Extended event channel support
Date: Tue, 2 Apr 2013 10:20:09 -0400 [thread overview]
Message-ID: <20130402142009.GF1754@phenom.dumpdata.com> (raw)
In-Reply-To: <515AA88F02000078000C9FE3@nat28.tlf.novell.com>
On Tue, Apr 02, 2013 at 08:44:47AM +0100, Jan Beulich wrote:
> >>> On 29.03.13 at 14:05, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> >> * 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.
>
> I don't think upstream inclusion of the Linux side patches is a
> requirement here. The patches need to exist (or else the code
> can't be tested), but there's no need for them to be in 3.10 as
> far as the interface selection if concerned.
>
OK.
next prev parent reply other threads:[~2013-04-02 14:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 11:23 Request for input: Extended event channel support George Dunlap
2013-03-27 19:36 ` Anil Madhavapeddy
2013-03-27 21:53 ` David Vrabel
2013-03-27 22:28 ` Anil Madhavapeddy
2013-03-27 22:31 ` Wei Liu
2013-03-28 12:51 ` Felipe Franciosi
2013-03-28 12:54 ` Anil Madhavapeddy
2013-03-28 13:02 ` Felipe Franciosi
2013-04-10 10:45 ` [Xen-users] " Ian Campbell
2013-04-10 16:14 ` Anil Madhavapeddy
2013-04-10 10:45 ` Ian Campbell
2013-03-28 1:56 ` Konrad Rzeszutek Wilk
2013-03-28 11:10 ` George Dunlap
2013-03-28 11:34 ` Jan Beulich
2013-03-29 13:05 ` Konrad Rzeszutek Wilk
2013-04-02 7:44 ` Jan Beulich
2013-04-02 14:20 ` Konrad Rzeszutek Wilk [this message]
2013-04-04 13:31 ` George Dunlap
2013-04-10 10:49 ` [Xen-users] " Ian Campbell
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=20130402142009.GF1754@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=dunlapg@umich.edu \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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 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.