From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Matthew Fioravante <matthew.fioravante@jhuapl.edu>,
Ian Campbell <Ian.Campbell@citrix.com>, Wei Liu <liuw@liuw.name>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jim Fehlig <jfehlig@suse.com>, Jan Beulich <JBeulich@suse.com>,
Anthony Perard <anthony.perard@citrix.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: Xen 4.3 development update, and stock-taking
Date: Tue, 22 Jan 2013 12:42:01 -0500 [thread overview]
Message-ID: <20130122174201.GD8365@phenom.dumpdata.com> (raw)
In-Reply-To: <50FD58FE.8050504@eu.citrix.com>
On Mon, Jan 21, 2013 at 03:04:30PM +0000, George Dunlap wrote:
> On 18/01/13 15:41, Konrad Rzeszutek Wilk wrote:
> >>Konrad Wilk: Persistent net grants, multi-page network, multi-page blk
> >a) persistent-page grants are in the Linux kernel.
> >
> >b) Multi-page network and persistent net grants.
> >Annie is doing a hollistic look at the network stack
> >and is going to setup a collaboration meeting between interested parties
> >(for right now I think it is Intel, Citrix, Amazon, SuSE, and Oracle)
> >to collaborate on that. There are multiple items in this and it would
> >be good that we don't step on each other toes.
> >
> >
> >c) Mutli-page block. That kind of morphed in me taking a hard look at the
> >block protocol itself and how we can fix this and other.
> >
> >http://lists.xen.org/archives/html/xen-devel/2012-12/msg01346.html
> >
> >Need more people to disuss and make sure we are actually on the
> >same page on the issues I enumerated.
> >
> >>Jim Fehlig: libvirt migration support
> >>
> >>Matthew Fioravante: vTPM
> >He posted some patches for the Linux kernel, but they need some tweaking.
> >..
> >>== Not yet complete ==
> >>
> >>* PVH mode (w/ Linux)
> >> owner: mukesh@oracle
> >> status (Linux): 3rd draft patches posted.
> >> status (Xen): RFC submitted
> >> prognosis: Good
> >The Linux side is good. The Xen hypervisor side needs reviews and
> >foremost the new hypercall needs to be set in stone (otherwsie
> >the Linux patches need to be redone).
>
> OK -- the main question for planning purposes is, does it seem like
> we can get this sorted out by the scheduled feature freeze on March
> 25? At the moment I'm going to leave this as "Good".
Aye.
>
> >
> >
> >.. snip..
> >>* Persistent grants for net
> >> owner: annie.li@citrix
> >> status: Initial implementation posted
> >> prognosis: ?
> >Shelved. The perf reports with Xen 4.2 did not show much improvement.
> >They should have but there is something amiss.
> >
> >goto b;
>
> OK -- so I'll put this down as "Not for 4.3".
Aye
>
> >>* Multi-page blk rings (external)
> >> - blkback in kernel (konrad@oracle, ?@intel)
> >> - qemu blkback
> >> status: Not started.
> >> prognosis: UNKNOWN
> >goto c;
>
> OK -- we still have a bit of time, so I'll leave this with Roger's
> assessment of "Fair" for now. We can always review the assessment
> later.
OK. Most of this (all of it?) is Linux related. So I would say that if you
are trying to hit the March deadline (which is when 3.9 merge window
opens), that means Roger has one month to code this up.
>
> >>* Multi-page net protocol (external)
> >> owner: ijc@citrix or annie.li@oracle
> >> status: Initial patches posted (by Wei Liu)
> >> expand the network ring protocol to allow multiple pages for
> >> increased throughput
> >goto b;
>
> OK -- I'll mark this as "Poor".
Aye.
>
> >We might also put on this list:
> >
> > - hardware performance counters.
> > Investigate what is important.
>
> This seems a bit to vague. How do I know when it can be crossed off? :-)
Deferred to Xen 4.4 then. Right now cooking up the list of items
we would like to do and see which ones can be part of GSOC (if any?)
>
> -George
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-01-22 17:42 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 17:55 Xen 4.3 development update, and stock-taking George Dunlap
2013-01-16 18:03 ` Matthew Fioravante
2013-01-18 15:19 ` Konrad Rzeszutek Wilk
2013-01-18 21:17 ` Fioravante, Matthew E.
2013-01-16 18:15 ` Wei Liu
2013-01-17 10:50 ` George Dunlap
2013-01-17 9:09 ` Jan Beulich
2013-01-17 11:12 ` George Dunlap
2013-01-17 12:51 ` Jan Beulich
2013-01-17 13:58 ` George Dunlap
2013-01-17 14:15 ` Jan Beulich
2013-01-17 14:32 ` George Dunlap
2013-01-17 15:26 ` Jan Beulich
2013-01-17 15:30 ` Jan Beulich
2013-01-17 15:48 ` George Dunlap
2013-01-17 16:04 ` George Dunlap
2013-01-17 16:20 ` Jan Beulich
2013-01-17 17:22 ` George Dunlap
2013-01-17 16:14 ` Jan Beulich
2013-01-17 16:29 ` George Dunlap
2013-01-17 16:49 ` Jan Beulich
2013-01-17 17:11 ` George Dunlap
2013-01-18 9:35 ` Jan Beulich
2013-01-17 16:43 ` George Dunlap
2013-01-17 17:06 ` Jan Beulich
2013-01-17 16:49 ` George Dunlap
2013-01-18 9:30 ` Jan Beulich
2013-01-18 15:24 ` Konrad Rzeszutek Wilk
2013-01-18 11:20 ` Daniel Kiper
2013-01-21 14:12 ` George Dunlap
2013-01-22 13:53 ` Daniel Kiper
2013-01-22 14:10 ` Jan Beulich
2013-01-18 15:22 ` Konrad Rzeszutek Wilk
2013-01-17 10:00 ` Roger Pau Monné
2013-01-17 11:22 ` George Dunlap
2013-01-18 9:50 ` Roger Pau Monné
2013-01-18 15:21 ` Konrad Rzeszutek Wilk
2013-01-18 15:33 ` Roger Pau Monné
2013-01-21 15:06 ` George Dunlap
2013-01-17 10:20 ` Olaf Hering
2013-01-17 17:23 ` George Dunlap
2013-01-17 15:54 ` Daniel De Graaf
2013-01-17 15:49 ` George Dunlap
2013-01-18 15:41 ` Konrad Rzeszutek Wilk
2013-01-21 15:04 ` George Dunlap
2013-01-22 17:42 ` Konrad Rzeszutek Wilk [this message]
[not found] <mailman.21508.1358358967.1399.xen-devel@lists.xen.org>
2013-01-17 16:07 ` Andres Lagar-Cavilla
-- strict thread matches above, loose matches on Subject: below --
2013-01-22 14:32 Daniel Kiper
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=20130122174201.GD8365@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=george.dunlap@eu.citrix.com \
--cc=jfehlig@suse.com \
--cc=liuw@liuw.name \
--cc=matthew.fioravante@jhuapl.edu \
--cc=roger.pau@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).