From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v27 1/2] migrate: Migrate TCP flows
Date: Mon, 17 Feb 2025 14:46:43 +1100 [thread overview]
Message-ID: <Z7KxI35CMdw-nPn7@zatzit> (raw)
In-Reply-To: <20250216222227.2017788-2-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
On Sun, Feb 16, 2025 at 11:22:26PM +0100, Stefano Brivio wrote:
> This implements flow preparation on the source, transfer of data with
> a format roughly inspired by struct tcp_tap_conn, plus a specific
> structure for parameters that don't fit in the flow table, and flow
> insertion on the target, with all the appropriate window options,
> window scaling, MSS, etc.
>
> Contents of pending queues are transferred as well.
>
> The target side is rather convoluted because we first need to create
> sockets and switch them to repair mode, before we can apply options
> that are *not* stored in the flow table. This also means that, if
> we're testing this on the same machine, in the same namespace, we need
> to close the listening socket on the source before we can start moving
> data.
>
> Further, we need to connect() the socket on the target before we can
> restore data queues, but we can't do that (again, on the same machine)
> as long as the matching source socket is open, which implies an
> arbitrary limit on queue sizes we can transfer, because we can only
> dump pending queues on the source as long as the socket is open, of
> course.
>
> Co-authored-by: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
The tests all pass for me, and while I can certainly see things that
can be improved, none are urgent.
Tested-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-02-17 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 22:22 [PATCH v27 0/2] State migration, perhaps final (#2)? Stefano Brivio
2025-02-16 22:22 ` [PATCH v27 1/2] migrate: Migrate TCP flows Stefano Brivio
2025-02-17 3:46 ` David Gibson [this message]
2025-02-16 22:22 ` [PATCH v27 2/2] test: Add migration tests Stefano Brivio
2025-02-17 3:47 ` 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=Z7KxI35CMdw-nPn7@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@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.
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).