From: Paolo Abeni <pabeni@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Cc: Bobby Eshleman <bobby.eshleman@bytedance.com>,
kvm@vger.kernel.org, netdev@vger.kernel.org,
Arseniy Krasnov <avkrasnov@salutedevices.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, oxffffaa@gmail.com,
Eric Dumazet <edumazet@google.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
kernel@sberdevices.ru, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v9 0/4] vsock/virtio/vhost: MSG_ZEROCOPY preparations
Date: Wed, 20 Sep 2023 13:06:48 +0200 [thread overview]
Message-ID: <f1198daa6d068c76b8ce692ad313698c34d0d1a3.camel@redhat.com> (raw)
In-Reply-To: <20230919223700-mutt-send-email-mst@kernel.org>
On Tue, 2023-09-19 at 22:38 -0400, Michael S. Tsirkin wrote:
> On Tue, Sep 19, 2023 at 03:35:51PM +0200, Stefano Garzarella wrote:
> > On Tue, Sep 19, 2023 at 03:19:54PM +0200, Paolo Abeni wrote:
> >
> > > DaveM suggests this should go via the virtio tree, too. Any different
> > > opinion?
> >
> > For this series should be fine, I'm not sure about the next series.
> > Merging this with the virtio tree, then it forces us to do it for
> > followup as well right?
> >
> > In theory followup is more on the core, so better with net-next, but
> > it's also true that for now only virtio transports support it, so it
> > might be okay to continue with virtio.
> >
> > @Michael WDYT?
> >
> > Thanks,
> > Stefano
>
> I didn't get DaveM's mail - was this off-list?
Yes, that was off-list co-ordination.
> I think net-next is easier because the follow up belongs in net-next.
> But if not I can take it, sure. Let me know.
Since there is agreement on that route, we will take it (likely
tomorrow).
Cheers,
Paolo
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2023-09-20 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230916130918.4105122-1-avkrasnov@salutedevices.com>
[not found] ` <20230916130918.4105122-5-avkrasnov@salutedevices.com>
2023-09-18 14:50 ` [PATCH net-next v9 4/4] vsock/virtio: MSG_ZEROCOPY flag support Stefano Garzarella
2023-09-18 17:27 ` [PATCH net-next v9 0/4] vsock/virtio/vhost: MSG_ZEROCOPY preparations Michael S. Tsirkin
[not found] ` <b5873e36-fe8c-85e8-e11b-4ccec386c015@salutedevices.com>
2023-09-19 7:54 ` Stefano Garzarella
2023-09-19 13:19 ` Paolo Abeni
2023-09-19 13:35 ` Stefano Garzarella
2023-09-20 2:38 ` Michael S. Tsirkin
2023-09-20 11:06 ` Paolo Abeni [this message]
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=f1198daa6d068c76b8ce692ad313698c34d0d1a3.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=avkrasnov@salutedevices.com \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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).