All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 release planning proposal
Date: Tue, 21 Aug 2012 10:26:12 -0400	[thread overview]
Message-ID: <20120821142611.GB20097@phenom.dumpdata.com> (raw)
In-Reply-To: <50335D8F.6000603@eu.citrix.com>

On Tue, Aug 21, 2012 at 11:06:07AM +0100, George Dunlap wrote:
> On 20/08/12 21:28, Konrad Rzeszutek Wilk wrote:
> >On Mon, Aug 20, 2012 at 05:46:59PM +0100, George Dunlap wrote:
> >>* Multi-page blk rings
> >>  - blkback in kernel (@intel)
> >.. and me as well.
> OK -- I think what I really need is just one person to be a
> point-of-contact, who can give updates on progress.  Shall I put you
> down for that, or should I find out who at Intel is working on it?

You can put me as contact person and I will keep track of
status.
> >>  - qemu blkback
> >>
> >>* Multi-page net protocol
> >>   owner: ?
> >>   expand the network ring protocol to allow multiple pages for
> >>   increased throughput
> >Multiple people working on this. Ian, me, Annie, and Wei I believe.
> OK -- Ian C said he'd be the primary point of contact for this one
> until Wei gets back; if you or Annie want to be the contact
> directly, let me know. :-)

Ian would be a better choice.

> >>* xl USB pass-through for PV guests
> >>   owner: ?
> >>   Port the xend PV pass-through functionality to xl.
> >Well, what about the Linux side? The frontend/backend drivers haven't
> >really been proposed for upstream.
> OK, I'll put that down as well.
> >>* PV audio (audio for stubdom qemu)
> >>   owner: stefano.panella@citrix
> >Is this a new person? Anyhow, there was a PV audio in pulseaudio as part
> >of the GSOC.
> Stefano Panella is on the XenClient team at Citrix.  I think he
> probably knows about the previous work, but I'll make sure.  One
> thing I know he's been particularly concerned about is audio
> latency, particularly with using GoToMeeting or Skype inside a VM.
> 
> Thanks,
>  -George
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

  reply	other threads:[~2012-08-21 14:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20 16:46 Xen 4.3 release planning proposal George Dunlap
2012-08-20 19:14 ` Pasi Kärkkäinen
2012-08-21 12:56   ` George Dunlap
2012-08-21 18:27     ` Pasi Kärkkäinen
2012-12-17 23:57   ` Martinx - ジェームズ
2012-12-18  7:03     ` Pasi Kärkkäinen
2012-12-18 13:37       ` Martinx - ジェームズ
2012-12-18 13:49         ` Jan Beulich
2012-08-20 20:28 ` Konrad Rzeszutek Wilk
2012-08-21 10:06   ` George Dunlap
2012-08-21 14:26     ` Konrad Rzeszutek Wilk [this message]
2012-08-21 14:43 ` Jan Beulich
2012-08-21 14:36   ` Attilio Rao
2012-08-21 14:55     ` Jan Beulich
2012-08-21 15:04   ` George Dunlap
2012-08-29 20:53 ` Dan Magenheimer
2012-08-30 10:24   ` Andrew Cooper
2012-08-30 10:53   ` David Vrabel
2012-08-30 16:11     ` Dan Magenheimer
2012-08-31 11:01       ` Jan Beulich
2012-08-31 17:59         ` Dan Magenheimer
     [not found] <mailman.11058.1345490072.1399.xen-devel@lists.xen.org>
2012-08-21 14:50 ` Andres Lagar-Cavilla
2012-08-21 18:44   ` Pasi Kärkkäinen

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=20120821142611.GB20097@phenom.dumpdata.com \
    --to=konrad@kernel.org \
    --cc=george.dunlap@eu.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 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.