Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752359Ab3GICRC (ORCPT ); Mon, 8 Jul 2013 22:17:02 -0400 Received: from ozlabs.org ([203.10.76.45]:37269 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751441Ab3GICRA (ORCPT ); Mon, 8 Jul 2013 22:17:00 -0400 From: Rusty Russell To: "Michael S. Tsirkin" , netdev@vger.kernel.org Cc: "David S. Miller" , Jason Wang , Cong Wang , Amos Kong , Dave Jones , virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] virtio-net: put virtio net header inline with data In-Reply-To: <20130708101259.GA16074@redhat.com> References: <20130708101259.GA16074@redhat.com> User-Agent: Notmuch/0.15.2+81~gd2c8818 (http://notmuchmail.org) Emacs/23.4.1 (i686-pc-linux-gnu) Date: Tue, 09 Jul 2013 11:46:23 +0930 Message-ID: <871u78eavc.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1167 Lines: 35 "Michael S. Tsirkin" writes: > For small packets we can simplify xmit processing > by linearizing buffers with the header: > most packets seem to have enough head room > we can use for this purpose. > Since existing hypervisors require that header > is the first s/g element, we need a feature bit > for this. > > Signed-off-by: Michael S. Tsirkin > --- > > Note: this needs to be applied on top of patch > defining VIRTIO_F_ANY_LAYOUT - bit to be > selected by Rusty. > > The following patch should work for any definition of > VIRTIO_F_ANY_LAYOUT - I used bit 31 for testing. > Rusty, could you please pick a valid bit for VIRTIO_F_ANY_LAYOUT > and squeeze this patch into 3.11? Sorry, it's too late. First, I've been a bit lax in sending patches via DaveM, and this is definitely his territory (ie. more net than virtio). Secondly, it needs baking and testing time. Cheers, Rusty. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/