This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Linux 2.6.39 - what Xen components went in.
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
Dkim-signature: v=1; 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; s=postfix; bh=CumtiYBm/ GyM7YjnnpSq2avY2pk=; b=jCZindoMmDahZH/tzoarDoXVJqHaUymSGdj7KvJLf 66oL9Qx8kojw5EMS0SpDSiGmvOeXbNk9v/AFCdDMp/Eh8OJvyo0L4KRF3Ca0nz5j aT3s+vWIi/UX09YnVJSNTPp8AJYXX0K5r7CNk6scyIz4esGb3n9EuALrHOKabKl5 uw=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110514150225.GA31761@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: GPLHost
References: <20110513143615.GA16193@xxxxxxxxxxxx> <BANLkTim_hgQ2qPWr9aZ8OtTrurz4LqA=jw@xxxxxxxxxxxxxx> <20110513164927.GA18484@xxxxxxxxxxxx> <4DCE4C45.8080706@xxxxxxxxxx> <20110514150225.GA31761@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110505 Icedove/3.0.11
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