[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1660267838.1945586-1-xuanzhuo@linux.alibaba.com>
Date: Fri, 12 Aug 2022 09:30:38 +0800
From: Xuan Zhuo <xuanzhuo@...ux.alibaba.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: virtualization@...ts.linux-foundation.org,
Jason Wang <jasowang@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
"Michael S. Tsirkin" <mst@...hat.com>
Subject: Re: [PATCH vhost 0/2] virtio_net: fix for stuck when change ring size with dev down
On Thu, 11 Aug 2022 10:37:30 -0700, Jakub Kicinski <kuba@...nel.org> wrote:
> On Thu, 11 Aug 2022 04:11:22 -0400 Michael S. Tsirkin wrote:
> > Which patches does this fix?
> > Maybe I should squash.
>
> Side question to make sure I understand the terminology - this
> is *not* a vhost patch, right? vhost is the host side of virtio?
> Is the work going via the vhost tree because of some dependencies?
Yes, the commits fixed by this patch are currently in Michael's vhost branch.
https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/log/?h=linux-next
So I mean that by "vhost" here, not into the net/net-next branch. Or should I use
a more accurate term next time?
Thanks.
Powered by blists - more mailing lists