From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
eperezma@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net V2] vhost: rewind next_avail_head while discarding descriptors
Date: Wed, 26 Nov 2025 01:27:48 -0500 [thread overview]
Message-ID: <20251126012023-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEuCgSVpshsdfeTwvRnMiY8WMEt8pT=gJ2A_=oiV188X0Q@mail.gmail.com>
On Wed, Nov 26, 2025 at 02:18:25PM +0800, Jason Wang wrote:
> On Wed, Nov 26, 2025 at 11:42 AM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > On Thu, 20 Nov 2025 10:29:50 +0800 Jason Wang wrote:
> > > Subject: [PATCH net V2] vhost: rewind next_avail_head while discarding descriptors
> >
> > > drivers/vhost/net.c | 53 ++++++++++++++++++------------
> > > drivers/vhost/vhost.c | 76 +++++++++++++++++++++++++++++++++++--------
> > > drivers/vhost/vhost.h | 10 +++++-
> >
> > Hm, is this targeting net because Michael is not planning any more PRs
> > for the 6.18 season?
>
> Basically because it touches vhost-net. I need inputs for which tree
> we should go for this and future modifications that touch both vhost
> core and vhost-net.
>
> Thanks
>
> >
Well this change is mostly net, vhost changes are just moving code
around. net tree gets more testing and more eyes looking at it, so it's
good for such cases.
--
MST
next prev parent reply other threads:[~2025-11-26 6:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 2:29 [PATCH net V2] vhost: rewind next_avail_head while discarding descriptors Jason Wang
2025-11-26 3:42 ` Jakub Kicinski
2025-11-26 6:18 ` Jason Wang
2025-11-26 6:27 ` Michael S. Tsirkin [this message]
2025-11-26 6:20 ` Michael S. Tsirkin
2025-11-26 23:00 ` patchwork-bot+netdevbpf
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=20251126012023-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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 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.