From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Eugenio Pérez" <eperezma@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,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH net-next v2 00/12] virtnet_net: prepare for af-xdp
Date: Fri, 31 May 2024 09:40:14 +0800 [thread overview]
Message-ID: <1717119614.404968-1-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <1717070084.6955814-1-xuanzhuo@linux.alibaba.com>
On Thu, 30 May 2024 19:54:44 +0800, Xuan Zhuo <xuanzhuo@linux.alibaba.com> wrote:
> On Thu, 30 May 2024 07:53:17 -0400, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > On Thu, May 30, 2024 at 07:23:54PM +0800, Xuan Zhuo wrote:
> > > This patch set prepares for supporting af-xdp zerocopy.
> > > There is no feature change in this patch set.
> > > I just want to reduce the patch num of the final patch set,
> > > so I split the patch set.
> > >
> > > Thanks.
> > >
> > > v2:
> > > 1. Add five commits. That provides some helper for sq to support premapped
> > > mode. And the last one refactors distinguishing xmit types.
> > >
> > > v1:
> > > 1. resend for the new net-next merge window
> > >
> >
> >
> > It's great that you are working on this but
> > I'd like to see the actual use of this first.
>
>
> For me, that is easy. But how should we do, if we use one patch set,
> then the commit number maybe 26, that exceeds 15 (limit of the net next).
Hi, Jakub
There will be a huge patch set (about 25) to support AF-XDP for virtio-net.
Can I just post this huge patch set if the maintainers of virtio-net agree?
Thanks.
>
> Thanks.
>
>
> >
> > >
> > > Xuan Zhuo (12):
> > > virtio_net: independent directory
> > > virtio_net: move core structures to virtio_net.h
> > > virtio_net: add prefix virtnet to all struct inside virtio_net.h
> > > virtio_net: separate virtnet_rx_resize()
> > > virtio_net: separate virtnet_tx_resize()
> > > virtio_net: separate receive_mergeable
> > > virtio_net: separate receive_buf
> > > virtio_ring: introduce vring_need_unmap_buffer
> > > virtio_ring: introduce dma map api for page
> > > virtio_ring: introduce virtqueue_dma_map_sg_attrs
> > > virtio_ring: virtqueue_set_dma_premapped() support to disable
> > > virtio_net: refactor the xmit type
> > >
> > > MAINTAINERS | 2 +-
> > > drivers/net/Kconfig | 9 +-
> > > drivers/net/Makefile | 2 +-
> > > drivers/net/virtio/Kconfig | 12 +
> > > drivers/net/virtio/Makefile | 8 +
> > > drivers/net/virtio/virtnet.h | 248 ++++++++
> > > .../{virtio_net.c => virtio/virtnet_main.c} | 596 +++++++-----------
> > > drivers/virtio/virtio_ring.c | 118 +++-
> > > include/linux/virtio.h | 12 +-
> > > 9 files changed, 606 insertions(+), 401 deletions(-)
> > > create mode 100644 drivers/net/virtio/Kconfig
> > > create mode 100644 drivers/net/virtio/Makefile
> > > create mode 100644 drivers/net/virtio/virtnet.h
> > > rename drivers/net/{virtio_net.c => virtio/virtnet_main.c} (93%)
> > >
> > > --
> > > 2.32.0.3.g01195cf9f
> >
>
next prev parent reply other threads:[~2024-05-31 1:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 11:23 [PATCH net-next v2 00/12] virtnet_net: prepare for af-xdp Xuan Zhuo
2024-05-30 11:23 ` [PATCH net-next v2 01/12] virtio_net: independent directory Xuan Zhuo
2024-05-30 11:23 ` [PATCH net-next v2 02/12] virtio_net: move core structures to virtio_net.h Xuan Zhuo
2024-05-30 11:23 ` [PATCH net-next v2 03/12] virtio_net: add prefix virtnet to all struct inside virtio_net.h Xuan Zhuo
2024-05-30 11:23 ` [PATCH net-next v2 04/12] virtio_net: separate virtnet_rx_resize() Xuan Zhuo
2024-05-30 11:23 ` [PATCH net-next v2 05/12] virtio_net: separate virtnet_tx_resize() Xuan Zhuo
2024-05-30 11:24 ` [PATCH net-next v2 06/12] virtio_net: separate receive_mergeable Xuan Zhuo
2024-05-30 11:24 ` [PATCH net-next v2 07/12] virtio_net: separate receive_buf Xuan Zhuo
2024-05-30 11:24 ` [PATCH net-next v2 08/12] virtio_ring: introduce vring_need_unmap_buffer Xuan Zhuo
2024-05-30 11:24 ` [PATCH net-next v2 09/12] virtio_ring: introduce dma map api for page Xuan Zhuo
2024-05-30 11:24 ` [PATCH net-next v2 10/12] virtio_ring: introduce virtqueue_dma_map_sg_attrs Xuan Zhuo
2024-05-30 11:24 ` [PATCH net-next v2 11/12] virtio_ring: virtqueue_set_dma_premapped() support to disable Xuan Zhuo
2024-05-30 11:24 ` [PATCH net-next v2 12/12] virtio_net: refactor the xmit type Xuan Zhuo
2024-06-02 19:50 ` Michael S. Tsirkin
2024-05-30 11:53 ` [PATCH net-next v2 00/12] virtnet_net: prepare for af-xdp Michael S. Tsirkin
2024-05-30 11:54 ` Xuan Zhuo
2024-05-31 1:40 ` Xuan Zhuo [this message]
2024-05-31 1:55 ` Jakub Kicinski
2024-05-31 1:57 ` Xuan Zhuo
2024-06-01 1:01 ` Xuan Zhuo
2024-06-02 19:49 ` 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=1717119614.404968-1-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--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=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
/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