From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@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: [PATCH net-next 0/7] virtnet_net: prepare for af-xdp
Date: Thu, 9 May 2024 09:58:13 +0800 [thread overview]
Message-ID: <1715219893.9627535-1-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <20240508082000.4938fb56@kernel.org>
On Wed, 8 May 2024 08:20:00 -0700, Jakub Kicinski <kuba@kernel.org> wrote:
> On Wed, 8 May 2024 09:53:08 +0100 Simon Horman wrote:
> > On Wed, May 08, 2024 at 04:05:07PM +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.
> > >
> > > #1-#3 add independent directory for virtio-net
> > > #4-#7 do some refactor, the sub-functions will be used by the subsequent commits
> >
> > Hi Xuan Zhuo,
> >
> > This patch is targeted at net-next,
> > but unfortunately it does not apply to current net-next.
> > Please rebase and repost taking care to observe the 24h rule.
>
> Also - is this going to conflict with your premapped DMA work in the
> vhost tree? If it does - just wait, please, the merge window is in
> a week..
NO.
This is on the top of
http://lore.kernel.org/all/20240508063718.69806-1-xuanzhuo@linux.alibaba.com
That is targeted to net-next.
I will wait until it is merged to repost.
Thanks.
next prev parent reply other threads:[~2024-05-09 2:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 8:05 [PATCH net-next 0/7] virtnet_net: prepare for af-xdp Xuan Zhuo
2024-05-08 8:05 ` [PATCH net-next 1/7] virtio_net: independent directory Xuan Zhuo
2024-05-08 8:05 ` [PATCH net-next 2/7] virtio_net: move core structures to virtio_net.h Xuan Zhuo
2024-05-08 8:05 ` [PATCH net-next 3/7] virtio_net: add prefix virtnet to all struct inside virtio_net.h Xuan Zhuo
2024-05-08 8:05 ` [PATCH net-next 4/7] virtio_net: separate virtnet_rx_resize() Xuan Zhuo
2024-05-08 8:05 ` [PATCH net-next 5/7] virtio_net: separate virtnet_tx_resize() Xuan Zhuo
2024-05-08 8:05 ` [PATCH net-next 6/7] virtio_net: separate receive_mergeable Xuan Zhuo
2024-05-08 8:05 ` [PATCH net-next 7/7] virtio_net: separate receive_buf Xuan Zhuo
2024-05-08 8:53 ` [PATCH net-next 0/7] virtnet_net: prepare for af-xdp Simon Horman
2024-05-08 15:20 ` Jakub Kicinski
2024-05-09 1:58 ` Xuan Zhuo [this message]
2024-05-23 2:26 ` 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=1715219893.9627535-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=hawk@kernel.org \
--cc=horms@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).