From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [PATCH] virtio-net: put virtio net header inline with data Date: Wed, 17 Jul 2013 15:32:36 +0930 Message-ID: <8761w9zptv.fsf@rustcorp.com.au> References: <8761wc38ea.fsf@rustcorp.com.au> <20130716.123326.798365002638711260.davem@davemloft.net> <20130717050032.GB10482@redhat.com> <20130716.220529.49723311269417873.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: amwang@redhat.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, davej@redhat.com To: David Miller , mst@redhat.com Return-path: In-Reply-To: <20130716.220529.49723311269417873.davem@davemloft.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org List-Id: netdev.vger.kernel.org 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.