From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Cc: Laurent Vivier <lvivier@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v5 0/6] Draft, incomplete series introducing state migration
Date: Wed, 5 Feb 2025 01:38:58 +0100 [thread overview]
Message-ID: <20250205003904.2797491-1-sbrivio@redhat.com> (raw)
This switches to the new facility with stages and introduces per-flow
migration, with a simple structure roughly based on struct
tcp_tap_conn.
I tested this: a simple connection between socat and nc with some text
works (again) for me. Sequence numbers (of course), window parameters,
and MSS all match.
However, it *is* draft quality and *it might contain bugs*.
It also contains a lot of TODO items, missing comments, probably
some left-overs, and so on.
David Gibson (2):
migrate: Make more handling common rather than vhost-user specific
migrate: Don't handle the migration channel through epoll
Stefano Brivio (4):
Introduce facilities for guest migration on top of vhost-user
infrastructure
Add interfaces and configuration bits for passt-repair
vhost_user: Make source quit after reporting migration state
Implement source and target sides of migration
Makefile | 14 +-
conf.c | 44 +++++-
epoll_type.h | 6 +-
flow.c | 226 +++++++++++++++++++++++++++++++
flow.h | 7 +
isolation.c | 2 +-
migrate.c | 291 ++++++++++++++++++++++++++++++++++++++++
migrate.h | 54 ++++++++
passt.1 | 11 ++
passt.c | 17 ++-
passt.h | 17 +++
repair.c | 193 ++++++++++++++++++++++++++
repair.h | 16 +++
tap.c | 65 +--------
tcp.c | 372 +++++++++++++++++++++++++++++++++++++++++++++++++++
tcp_conn.h | 59 ++++++++
util.c | 62 +++++++++
util.h | 27 ++++
vhost_user.c | 69 +++-------
virtio.h | 4 -
vu_common.c | 49 +------
vu_common.h | 2 +-
22 files changed, 1427 insertions(+), 180 deletions(-)
create mode 100644 migrate.c
create mode 100644 migrate.h
create mode 100644 repair.c
create mode 100644 repair.h
--
2.43.0
next reply other threads:[~2025-02-05 0:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 0:38 Stefano Brivio [this message]
2025-02-05 0:38 ` [PATCH v5 1/6] Introduce facilities for guest migration on top of vhost-user infrastructure Stefano Brivio
2025-02-05 1:44 ` David Gibson
2025-02-05 0:39 ` [PATCH v5 2/6] migrate: Make more handling common rather than vhost-user specific Stefano Brivio
2025-02-05 0:39 ` [PATCH v5 3/6] migrate: Don't handle the migration channel through epoll Stefano Brivio
2025-02-05 0:39 ` [PATCH v5 4/6] Add interfaces and configuration bits for passt-repair Stefano Brivio
2025-02-05 0:39 ` [PATCH v5 5/6] vhost_user: Make source quit after reporting migration state Stefano Brivio
2025-02-05 2:09 ` David Gibson
2025-02-05 5:47 ` Stefano Brivio
2025-02-05 8:58 ` Hanna Czenczek
2025-02-05 10:19 ` Stefano Brivio
2025-02-05 11:39 ` David Gibson
2025-02-05 0:39 ` [PATCH v5 6/6] Implement source and target sides of migration Stefano Brivio
2025-02-05 1:10 ` 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=20250205003904.2797491-1-sbrivio@redhat.com \
--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).