From: Stefan Hajnoczi <stefanha@gmail.com>
To: Hanna Czenczek <hreitz@redhat.com>
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
virtio-fs-list <virtio-fs@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Dave Gilbert" <dgilbert@redhat.com>,
"Juan Quintela" <quintela@redhat.com>
Subject: Re: [Virtio-fs] vhost-user (virtio-fs) migration: back end state
Date: Wed, 8 Feb 2023 11:32:53 -0500 [thread overview]
Message-ID: <CAJSP0QWrw0o6Mym02vc42TLOdY7mFKH1xQvf=n23J4eOhHWwpg@mail.gmail.com> (raw)
In-Reply-To: <d33b0bff-f07d-56a9-8648-16310b60f8a5@redhat.com>
On Wed, 8 Feb 2023 at 10:58, Hanna Czenczek <hreitz@redhat.com> wrote:
>
> On 08.02.23 15:32, Stefan Hajnoczi wrote:
> > On Tue, 7 Feb 2023 at 07:29, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> >> On Tue, 7 Feb 2023 at 04:08, Hanna Czenczek <hreitz@redhat.com> wrote:
> >>> On 06.02.23 17:27, Stefan Hajnoczi wrote:
> >>>> On Mon, 6 Feb 2023 at 07:36, Hanna Czenczek <hreitz@redhat.com> wrote:
> >>>> Should we schedule a call with Jason, Michael, Juan, David, etc to
> >>>> discuss further? That way there's less chance of spending weeks
> >>>> working on something only to be asked to change the approach later.
> >>> Sure, sounds good! I’ve taken a look into what state we’ll need to
> >>> migrate already, but I’ll take a more detailed look now so that it’s
> >>> clear what our requirements are.
> > Hi Hanna,
> > The next step is getting agreement on how the vhost-user device state
> > interface will work. Do you want to draft the new vhost-user protocol
> > messages and put together slides for discussion with Michael, Jason,
> > Juan, and David in the next KVM call? That might be the best way to
> > get agreement. Doing it via email is possible too but I guess it will
> > take longer.
> >
> > If you don't want to design the vhost-user protocol changes yourself
> > then someone on this email thread can help with that.
>
> I’ll need to talk about the whole thing to Stefano and German first
> (we’re collaborating on virtio-fs migration, looking at different
> aspects of it). Also, I think I’ll want to look into the code a bit
> first and fiddle around to get a working prototype so I get an idea of
> what might be feasible at all. I wouldn’t want to propose something
> that actually can’t work when I try to make it work in practice. O:)
Okay.
The specifics of the virtiofs device state don't need much discussion
here. Only the vhost-user protocol changes need agreement because they
are generic infrastructure that will affect other vhost-user device
types, vDPA, and probably core VIRTIO. So don't worry about defining
what each piece of virtiofs state needs to be at this point, I guess
you only need a rough idea in order to come up with the vhost-user
protocol changes.
Stefan
prev parent reply other threads:[~2023-02-08 16:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 12:35 [Virtio-fs] vhost-user (virtio-fs) migration: back end state Hanna Czenczek
2023-02-06 16:27 ` Stefan Hajnoczi
2023-02-06 21:02 ` Juan Quintela
2023-02-06 21:16 ` Stefan Hajnoczi
2023-02-06 23:58 ` Juan Quintela
2023-02-07 9:35 ` Hanna Czenczek
2023-02-07 15:13 ` Juan Quintela
2023-02-07 9:08 ` Hanna Czenczek
2023-02-07 12:29 ` Stefan Hajnoczi
2023-02-08 14:32 ` Stefan Hajnoczi
2023-02-08 14:34 ` Michael S. Tsirkin
2023-02-08 15:58 ` Hanna Czenczek
2023-02-08 16:32 ` Stefan Hajnoczi [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='CAJSP0QWrw0o6Mym02vc42TLOdY7mFKH1xQvf=n23J4eOhHWwpg@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=dgilbert@redhat.com \
--cc=eperezma@redhat.com \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-fs@redhat.com \
/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).