Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751927Ab3GOEXj (ORCPT ); Mon, 15 Jul 2013 00:23:39 -0400 Received: from ozlabs.org ([203.10.76.45]:34587 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751384Ab3GOEXi (ORCPT ); Mon, 15 Jul 2013 00:23:38 -0400 From: Rusty Russell To: "Michael S. Tsirkin" Cc: netdev@vger.kernel.org, "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: <20130710061407.GC19759@redhat.com> References: <20130708101259.GA16074@redhat.com> <871u78eavc.fsf@rustcorp.com.au> <20130709051824.GA3234@redhat.com> <87vc4kcfzg.fsf@rustcorp.com.au> <20130710061407.GC19759@redhat.com> User-Agent: Notmuch/0.15.2+81~gd2c8818 (http://notmuchmail.org) Emacs/23.4.1 (i686-pc-linux-gnu) Date: Mon, 15 Jul 2013 11:10:41 +0930 Message-ID: <878v1838iu.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: 2362 Lines: 69 "Michael S. Tsirkin" writes: > On Tue, Jul 09, 2013 at 05:38:51PM +0930, Rusty Russell wrote: >> "Michael S. Tsirkin" writes: >> > On Tue, Jul 09, 2013 at 11:46:23AM +0930, Rusty Russell wrote: >> >> "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). >> > >> > Let's do this: I'll send a patch series, you ack and we see >> > what happens? >> >> If you convince DaveM, I won't object :) >> >> >> Secondly, it needs baking and testing time. >> >> >> >> Cheers, >> >> Rusty. >> > >> > I did some testing on this. But proper testing just isn't happening out >> > of tree. >> >> But it will get into linux-next for the *next* merge window. >> >> Cheers, >> Rusty. > > Okay. Can you put it on virtio-next then? > I don't see it there ... Here's the general order: - 1 week before Linus merge window: I stop putting new stuff into xxx-next. - Linus merge window open: I push stuff to Linus, new stuff stays in -pending. - Linus merge window close: I ff my -next trees to -rc1, merge stuff from -pending. In this case, your patch will go from pending-rebases to DaveM, not virtio-next. Which I will do now... 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/