[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130716.220529.49723311269417873.davem@davemloft.net>
Date: Tue, 16 Jul 2013 22:05:29 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: mst@...hat.com
Cc: rusty@...tcorp.com.au, netdev@...r.kernel.org, jasowang@...hat.com,
amwang@...hat.com, akong@...hat.com, davej@...hat.com,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] virtio-net: put virtio net header inline with data
From: "Michael S. Tsirkin" <mst@...hat.com>
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 <rusty@...tcorp.com.au>
>> Date: Mon, 15 Jul 2013 11:13:25 +0930
>>
>> > From: Michael S. Tsirkin <mst@...hat.com>
>> >
>> > 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 <mst@...hat.com>
>> > Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>
>>
>> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists