From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Mszb2-0006Fz-Uo
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 09:51:57 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Mszat-0006BO-Df
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 09:51:52 -0400
Received: from [199.232.76.173] (port=46237 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Mszat-0006BD-5u
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 09:51:47 -0400
Received: from bombadil.infradead.org ([18.85.46.34]:36337)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from
	<BATV+3daa9655a1c8c11dee4c+2229+infradead.org+hch@bombadil.srs.infradead.org>)
	id 1Mszas-0005x8-Kk
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 09:51:46 -0400
Date: Wed, 30 Sep 2009 09:51:44 -0400
From: Christoph Hellwig <hch@infradead.org>
Message-ID: <20090930135144.GA29956@infradead.org>
References: <1241459088.26045.1.camel@lappy>
	<1241513785-28738-1-git-send-email-markmc@redhat.com>
	<1254257151.29022.11.camel@blaa>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1254257151.29022.11.camel@blaa>
Subject: [Qemu-devel] Re: [PATCH 1/1] qemu-kvm: virtio-net: Re-instate GSO
	code removed upstream
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Mark McLoughlin <markmc@redhat.com>
Cc: avi@redhat.com, kvm@vger.kernel.org, qemu-devel@nongnu.org

I might sound like a broken record, but why isn't the full GSO support
for virtio-net upstream in qemu?