From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 development update, and stock-taking
Date: Fri, 18 Jan 2013 10:21:47 -0500 [thread overview]
Message-ID: <20130118152147.GB9973@phenom.dumpdata.com> (raw)
In-Reply-To: <50F91AF6.4020400@citrix.com>
On Fri, Jan 18, 2013 at 10:50:46AM +0100, Roger Pau Monné wrote:
> On 17/01/13 12:22, George Dunlap wrote:
> > On 17/01/13 10:00, Roger Pau Monne wrote:
> >> On 16/01/13 18:55, George Dunlap wrote:
> >>> * Persistent grants for blk (external)
> >>> owner: roger.pau@citrix
> >>> status: Initial implementation posted
> >>> prognosis: ?
> >> Done, Linux implementation scheduled for 3.8, and Qemu side is also done
> >> and being upstreamed right now.
> >
> > OK, so I'll mark the Linux component as "done", and the qemu component
> > as "Good".
> >
> >>> * Persistent grants for net
> >>> owner: annie.li@citrix
> >>> status: Initial implementation posted
> >>> prognosis: ?
> >>>
> >>> * Multi-page blk rings (external)
> >>> - blkback in kernel (konrad@oracle, ?@intel)
> >>> - qemu blkback
> >>> status: Not started.
> >>> prognosis: UNKNOWN
> >> I will be taking on this project, following Intel, FreeBSD and Konrad
> >> suggestions. Since I'm just starting now, I will mark it as "Fair".
> >
> > OK, thanks for the info. Out of curiosity, if someone were to consider
> > this a blocker, would having someone else working on it speed things up,
> > do you think? Or is it development probably "non-parallelizable"? :-)
>
> Let's wait until we have a clear roadmap about how are we going to
> handle it. This is not related to Xen itself, so I wouldn't see it as a
> blocker, most of the work will be done in the Linux kernel, and the only
> hypervisor part of this might be changes to the block protocol (blkif.h)
> and the ring (ring.h) protocol.
Did you have a chance to look at the issues I enumerated with the block
protocol?
Perhaps we should continue the discussion on the "clear roadmap" on that
thread?
next prev parent reply other threads:[~2013-01-18 15:21 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 [this message]
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
[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=20130118152147.GB9973@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--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).