public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
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: Re: [PATCH v3 00/20] Draft, incomplete series introducing state migration
Date: Sat, 1 Feb 2025 08:45:18 +0100	[thread overview]
Message-ID: <20250201084518.04689645@elisabeth> (raw)
In-Reply-To: <20250131193953.3034031-1-sbrivio@redhat.com>

On Fri, 31 Jan 2025 20:39:33 +0100
Stefano Brivio <sbrivio@redhat.com> wrote:

> What clearly needs changes:

Maybe something less elegant but actually functional like:

---
static int migrate_data_v1(int fd, struct ctx *c, bool target)
{
	struct iovec context[] { /* All these need to be network endian */
		c->hash_secret,		sizeof(c->hash_secret),
		c->ipv4.addr_seen,	sizeof(c->ipv4.addr_seen),
		c->ipv6.addr_seen,	sizeof(c->ipv6.addr_seen),
		c->ipv6.addr_ll_seen,	sizeof(c->ipv6.addr_ll_seen),
		/* Leave NDP's next_ra alone, start from 0 */
		&log_written /* Drop static */ sizeof(log_written),
	};
	int rc;

	if (target)
		rc = read_remainder(fd, context, ARRAY_SIZE(context), 0);
	else
		rc = write_remainder(fd, context, ARRAY_SIZE(context), 0);

	if (rc)
		return errno;

	if (target)
		return flow_migrate_data_target_v1(fd, c);
	return flow_migrate_data_source_v1(fd, c);
}
---

and:

---
struct tcp_flow_transfer_v1 {
	struct flow_common f;

	uint8_t retrans;

	uint16_t ws_from_tap; /* All BE */
	uint16_t ws_to_tap;
	uint16_t tap_mss;

	...
} __attribute__((packed));

union flow_transfer_v1 {
	struct tcp_flow_transfer_v1 tcp;
	...
};

int flow_migrate_data_source_v1(int fd, struct ctx *c)
{
	for_each_active_flow(flowtab) {
		union flow_transfer_v1 d;

		switch (flow->f.type) {
		case FLOW_TCP:
			d.tcp.f = flow->f;
			d.tcp.retrans = flow->tcp.retrans;
			d.tcp.ws_from_tap = htons(d.tcp.ws_from_tap);
			...;

			/* Fetch window stuff, socket must be in repair mode */

		send(...);
	}

int flow_migrate_data_target_v1(int fd, struct ctx *c)
{
	...
}

And I'm not sure about "[PATCH 0/2] Fancier version handling for
migration": perhaps we could switch to something radically easier
from the beginning. I mean, as we have to drop the declarative
approach altogether, at least let's minimise LoCs...

-- 
Stefano


      parent reply	other threads:[~2025-02-01  7:45 UTC|newest]

Thread overview: 22+ 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-01-31 19:39 ` [PATCH v3 09/20] Add interfaces and configuration bits for passt-repair Stefano Brivio
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-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-01-31 19:39 ` [PATCH v3 17/20] vhost_user: Make source quit after reporting migration state 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-01-31 19:39 ` [PATCH v3 19/20] tcp: Add HOSTSIDE(x), HOSTFLOW(x) macros Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 20/20] Implement target side of migration Stefano Brivio
2025-02-01  7:45 ` Stefano Brivio [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=20250201084518.04689645@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).