From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH v3 14/20] migrate: Don't handle the migration channel through epoll
Date: Mon, 3 Feb 2025 06:38:56 +0100 [thread overview]
Message-ID: <20250203063856.0d08f579@elisabeth> (raw)
In-Reply-To: <Z6Ag3ELdX9WnZJsi@zatzit>
On Mon, 3 Feb 2025 12:50:20 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Fri, Jan 31, 2025 at 08:39:47PM +0100, Stefano Brivio wrote:
> > From: David Gibson <david@gibson.dropbear.id.au>
> >
> > Currently, once a migration device state fd is assigned, we wait for
> > EPOLLIN or EPOLLOUT events on it to actually perform the migration. Change
> > it so that once a migration is requested it we complete it synchronously
> > at the end of the current epoll cycle. This has several advantages:
> >
> > 1. It makes it clear that everything about the migration must be dealt
> > with at once, not split between multiple epoll events on the channel
> > 2. It ensures the migration always takes place between epoll cycles,
> > rather than, for example, between handling TCP events and their
> > deferred handling in post_handler().
> > 3. It reduces code setting up the epoll watch on the fd.
> >
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > ---
> > epoll_type.h | 2 --
> > migrate.c | 44 +++++++++++---------------------------------
> > migrate.h | 2 +-
> > passt.c | 6 ++----
> > passt.h | 2 ++
> > vu_common.c | 27 +++++++++++++++++++++++++++
> > 6 files changed, 43 insertions(+), 40 deletions(-)
> >
> > diff --git a/epoll_type.h b/epoll_type.h
> > index b981d30..7f2a121 100644
> > --- a/epoll_type.h
> > +++ b/epoll_type.h
> > @@ -40,8 +40,6 @@ enum epoll_type {
> > EPOLL_TYPE_VHOST_CMD,
> > /* vhost-user kick event socket */
> > EPOLL_TYPE_VHOST_KICK,
> > - /* migration device state channel */
> > - EPOLL_TYPE_DEVICE_STATE,
> > /* TCP_REPAIR helper listening socket */
> > EPOLL_TYPE_REPAIR_LISTEN,
> > /* TCP_REPAIR helper socket */
> > diff --git a/migrate.c b/migrate.c
> > index fc6a043..faa7841 100644
> > --- a/migrate.c
> > +++ b/migrate.c
> > @@ -50,7 +50,6 @@ static union migrate_header header = {
> >
> > /* Data sections for version 1 */
> > static struct iovec sections_v1[] = {
> > - { &header, sizeof(header) },
>
> This hunk seems to have migrated in during rebase somehow, it wasn't
> in my original patch, and it breaks compile.
Oh, oops, yes. I did one last rebase round before posting, and I was
convinced I was just rewording messages, so I didn't even try to
rebuild, but obviously I moved some code here and there as well.
Do you prefer I post a v4 fixing this up and addressing your other
comments (and some of my open points), or should I rather wait, if
you're working on patches based on v3? It makes no difference to me.
--
Stefano
next prev parent reply other threads:[~2025-02-03 5:39 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 19:39 [PATCH v3 00/20] Draft, incomplete series introducing state migration Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 01/20] tcp: Always pass NULL event with EPOLL_CTL_DEL Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 02/20] util: Rename and make global vu_remove_watch() Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 03/20] icmp, udp: Pad time_t timestamp to 64-bit to ease state migration Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 04/20] flow, flow_table: Pad flow table entries to 128 bytes, hash entries to 32 bits Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 05/20] flow_table: Use size in extern declaration for flowtab Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 06/20] util: Add read_remainder() and read_all_buf() Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 07/20] Introduce facilities for guest migration on top of vhost-user infrastructure Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 08/20] Introduce passt-repair Stefano Brivio
2025-02-03 1:46 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 09/20] Add interfaces and configuration bits for passt-repair Stefano Brivio
2025-02-03 5:22 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 10/20] flow, tcp: Basic pre-migration source handler to dump sequence numbers Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 11/20] migrate: vu_migrate_{source,target}() aren't actually vu speciic Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 12/20] migrate: Move repair_sock_init() to vu_init() Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 13/20] migrate: Make more handling common rather than vhost-user specific Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 14/20] migrate: Don't handle the migration channel through epoll Stefano Brivio
2025-02-03 1:50 ` David Gibson
2025-02-03 5:38 ` Stefano Brivio [this message]
2025-02-03 8:45 ` David Gibson
2025-02-03 2:16 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 15/20] flow, flow_table: Export declaration of hash table Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 16/20] vhost_user: Turn vhost-user message reports to trace() Stefano Brivio
2025-02-03 3:11 ` David Gibson
2025-02-03 6:10 ` Stefano Brivio
2025-02-03 8:47 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 17/20] vhost_user: Make source quit after reporting migration state Stefano Brivio
2025-02-03 1:55 ` David Gibson
2025-02-03 6:09 ` Stefano Brivio
2025-02-03 8:52 ` David Gibson
2025-02-03 9:44 ` Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 18/20] tcp: Get our socket port using getsockname() when connecting from guest Stefano Brivio
2025-02-03 2:05 ` David Gibson
2025-02-03 6:09 ` Stefano Brivio
2025-02-03 8:59 ` David Gibson
2025-02-03 9:45 ` Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 19/20] tcp: Add HOSTSIDE(x), HOSTFLOW(x) macros Stefano Brivio
2025-02-03 2:06 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 20/20] Implement target side of migration Stefano Brivio
2025-02-01 7:45 ` [PATCH v3 00/20] Draft, incomplete series introducing state migration Stefano Brivio
2025-02-03 2:18 ` David Gibson
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=20250203063856.0d08f579@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).