[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Linux 2.6.39 - what Xen components went in.

  • To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • From: Thomas Goirand <thomas@xxxxxxxxxx>
  • Date: Sun, 15 May 2011 12:32:48 +0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 14 May 2011 21:34:13 -0700
  • Domainkey-signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=Kct MFdI42w39ll0+fYmpw/1SCylheJ/16nURd7WaPumH/+vOZ/7iq1kFjSEq4JCY+70 /UqfGxEHcK7skc0zMpaTt2GXz2L5Co9Wl2MKhyGsxxKPsdISDIGYL7dDrKdxJm+e Dv8OFMvJ93TyKdYq5QSu8jlP4yUJe3QEDV7PbMaQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 05/14/2011 11:02 PM, Konrad Rzeszutek Wilk wrote:
> On Sat, May 14, 2011 at 05:32:53PM +0800, Thomas Goirand wrote:
>> On 05/14/2011 12:49 AM, Konrad Rzeszutek Wilk wrote:
>>>> I assume this means that drivers/block/xen-blkback.c is the last major
>>>> milestone to be pushed upstream?
>>> There are also some semi-major ones, but right now the xen-blkback is 
>>> important
>>> since it provides so much more performance benefit than the QEMU one.
>> Thanks a lot Konrad, for the report.
>> Can you tell what the problem was with of xen-blkback.c?
> Not sure I understand you. Then xen block backend (so 
> drivers/block/xen-blkback/*)
> is going through review on LKML?

Sorry, let me rephrase: why has drivers/block/xen-blkback.c not been
upstreamed to kernel.org yet? What was the blocker(s)? LKLM is a very
busy list, hard to follow...


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.