Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758096Ab3GRBXp (ORCPT ); Wed, 17 Jul 2013 21:23:45 -0400 Received: from ozlabs.org ([203.10.76.45]:42348 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758020Ab3GRBXn (ORCPT ); Wed, 17 Jul 2013 21:23:43 -0400 From: Rusty Russell To: David Miller , mst@redhat.com Cc: netdev@vger.kernel.org, jasowang@redhat.com, amwang@redhat.com, akong@redhat.com, davej@redhat.com, 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: <20130716.220529.49723311269417873.davem@davemloft.net> References: <8761wc38ea.fsf@rustcorp.com.au> <20130716.123326.798365002638711260.davem@davemloft.net> <20130717050032.GB10482@redhat.com> <20130716.220529.49723311269417873.davem@davemloft.net> User-Agent: Notmuch/0.15.2+81~gd2c8818 (http://notmuchmail.org) Emacs/23.4.1 (i686-pc-linux-gnu) Date: Wed, 17 Jul 2013 15:32:36 +0930 Message-ID: <8761w9zptv.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: 1811 Lines: 49 David Miller writes: > From: "Michael S. Tsirkin" > Date: Wed, 17 Jul 2013 08:00:32 +0300 > >> On Tue, Jul 16, 2013 at 12:33:26PM -0700, David Miller wrote: >>> From: Rusty Russell >>> Date: Mon, 15 Jul 2013 11:13:25 +0930 >>> >>> > From: Michael S. Tsirkin >>> > >>> > 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 >>> > Signed-off-by: Rusty Russell >>> >>> I really think this has to wait until the next merge window, sorry. >>> >>> Please resubmit this when I open net-next back up, thanks. >> >> I assumed since -rc1 is out net-next is already open? > > -rc1 being released never makes net-next open. Instead, I explicitly > open it up at some point in time after -rc1 when I feel that things > have settled down enough. > > And when that happens, I announce so here. > > So you have to follow my announcements here on netdev to know > when net-next is actually open. Thanks for letting me know. I'm sure that works well for others, but I can't follow the mailing lists of every maintainer I deal with. Fortunately, you're the paragon for acking applied patches, so if I hit this failure mode again I will know. 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/