netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jason Wang <jasowang@redhat.com>
Cc: "Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Jesper Dangaard Brouer" <hawk@kernel.org>,
	"John Fastabend" <john.fastabend@gmail.com>,
	virtualization@lists.linux.dev, bpf@vger.kernel.org
Subject: Re: [RFC net-next 00/13] virtio-net: support AF_XDP zero copy (tx)
Date: Mon, 22 Jul 2024 17:42:04 -0700	[thread overview]
Message-ID: <20240722174204.0eedd139@kernel.org> (raw)
In-Reply-To: <CACGkMEsX5CwQmrwYzosSDMRdOfYVEmaL6x0-M9fWq0whwyRwSQ@mail.gmail.com>

On Mon, 22 Jul 2024 15:27:42 +0800 Jason Wang wrote:
> I wonder why this series is tagged as "RFC"?

I guess it's because net-next is closed during merge window.
I understand that the situation is somewhat special 
because we got Rx merged but not Tx.
Do you think this is ready for v6.11 with high confidence?

  reply	other threads:[~2024-07-23  0:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16  6:46 [RFC net-next 00/13] virtio-net: support AF_XDP zero copy (tx) Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 01/13] virtio_ring: introduce vring_need_unmap_buffer Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 02/13] virtio_ring: split: harden dma unmap for indirect Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 03/13] virtio_ring: packed: " Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 04/13] virtio_ring: perform premapped operations based on per-buffer Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 05/13] virtio-net: rq submits premapped buffer per buffer Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 06/13] virtio_ring: remove API virtqueue_set_dma_premapped Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 07/13] virtio_net: refactor the xmit type Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 08/13] virtio_net: xsk: bind/unbind xsk for tx Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 09/13] virtio_net: xsk: prevent disable tx napi Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 10/13] virtio_net: xsk: tx: support xmit xsk buffer Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 11/13] virtio_net: xsk: tx: handle the transmitted " Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 12/13] virtio_net: update tx timeout record Xuan Zhuo
2024-07-16  6:46 ` [RFC net-next 13/13] virtio_net: xdp_features add NETDEV_XDP_ACT_XSK_ZEROCOPY Xuan Zhuo
2024-07-22  7:27 ` [RFC net-next 00/13] virtio-net: support AF_XDP zero copy (tx) Jason Wang
2024-07-23  0:42   ` Jakub Kicinski [this message]
2024-07-23  1:20     ` Xuan Zhuo

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=20240722174204.0eedd139@kernel.org \
    --to=kuba@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=hawk@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).