All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: David Miller <davem@davemloft.net>, mst@redhat.com
Cc: amwang@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, davej@redhat.com
Subject: Re: [PATCH] virtio-net: put virtio net header inline with data
Date: Wed, 17 Jul 2013 15:32:36 +0930	[thread overview]
Message-ID: <8761w9zptv.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130716.220529.49723311269417873.davem@davemloft.net>

David Miller <davem@davemloft.net> writes:
> From: "Michael S. Tsirkin" <mst@redhat.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@rustcorp.com.au>
>>> Date: Mon, 15 Jul 2013 11:13:25 +0930
>>> 
>>> > From: Michael S. Tsirkin <mst@redhat.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@redhat.com>
>>> > Signed-off-by: Rusty Russell <rusty@rustcorp.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.

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.

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: David Miller <davem@davemloft.net>, 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
Date: Wed, 17 Jul 2013 15:32:36 +0930	[thread overview]
Message-ID: <8761w9zptv.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130716.220529.49723311269417873.davem@davemloft.net>

David Miller <davem@davemloft.net> writes:
> From: "Michael S. Tsirkin" <mst@redhat.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@rustcorp.com.au>
>>> Date: Mon, 15 Jul 2013 11:13:25 +0930
>>> 
>>> > From: Michael S. Tsirkin <mst@redhat.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@redhat.com>
>>> > Signed-off-by: Rusty Russell <rusty@rustcorp.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.

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.

  reply	other threads:[~2013-07-17  6:02 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 10:12 [PATCH] virtio-net: put virtio net header inline with data Michael S. Tsirkin
2013-07-08 10:12 ` Michael S. Tsirkin
2013-07-09  2:16 ` Rusty Russell
2013-07-09  2:16   ` Rusty Russell
2013-07-09  5:18   ` Michael S. Tsirkin
2013-07-09  5:18     ` Michael S. Tsirkin
2013-07-09  8:08     ` Rusty Russell
2013-07-09  8:08       ` Rusty Russell
2013-07-10  4:38       ` David Miller
2013-07-10  4:38         ` David Miller
2013-07-15  1:43         ` Rusty Russell
2013-07-15  1:43           ` Rusty Russell
2013-07-16 19:33           ` David Miller
2013-07-16 19:33             ` David Miller
2013-07-17  0:08             ` Rusty Russell
2013-07-17  0:08               ` Rusty Russell
2013-07-17  5:00             ` Michael S. Tsirkin
2013-07-17  5:00               ` Michael S. Tsirkin
2013-07-17  5:05               ` David Miller
2013-07-17  5:05                 ` David Miller
2013-07-17  6:02                 ` Rusty Russell [this message]
2013-07-17  6:02                   ` Rusty Russell
2013-07-24 19:44                   ` Michael S. Tsirkin
2013-07-24 19:44                     ` Michael S. Tsirkin
2013-07-10  6:14       ` Michael S. Tsirkin
2013-07-10  6:14         ` Michael S. Tsirkin
2013-07-15  1:40         ` Rusty Russell
2013-07-15  1:40           ` Rusty Russell
2013-07-11 13:00   ` Michael S. Tsirkin
2013-07-11 13:00     ` [Qemu-devel] " Michael S. Tsirkin
2013-07-11 13:00     ` Michael S. Tsirkin
2013-07-12  5:57     ` Rusty Russell
2013-07-12  5:57       ` [Qemu-devel] " Rusty Russell
2013-07-12  5:57       ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2013-06-06  9:55 Michael S. Tsirkin
2013-06-06 19:59 ` [Qemu-devel] " Jesse Larrew
2013-06-06 20:09   ` Dave Jones
2013-06-06 20:18     ` Jesse Larrew
2013-06-07  2:12 ` Rusty Russell
2013-06-09  7:11   ` Michael S. Tsirkin
2013-06-09  7:11     ` Michael S. Tsirkin
2013-06-07  2:52 ` Jason Wang
2013-06-07  2:52   ` Jason Wang
2013-06-09  6:52   ` Michael S. Tsirkin
2013-06-09  6:52     ` Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761w9zptv.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=amwang@redhat.com \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.