public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v13 5/6] migrate: Migrate TCP flows
Date: Mon, 10 Feb 2025 16:54:37 +0100	[thread overview]
Message-ID: <20250210165437.0defc859@elisabeth> (raw)
In-Reply-To: <20250210105131.5403ae1b@elisabeth>

On Mon, 10 Feb 2025 10:51:31 +0100
Stefano Brivio <sbrivio@redhat.com> wrote:

> On Mon, 10 Feb 2025 17:05:08 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > On Sun, Feb 09, 2025 at 11:20:04PM +0100, Stefano Brivio wrote:  
> > >
> > > +++ b/migrate.c
> > > @@ -98,11 +98,30 @@ static int seen_addrs_target_v1(struct ctx *c,
> > >  
> > >  /* Stages for version 1 */
> > >  static const struct migrate_stage stages_v1[] = {
> > > +	/* FIXME: With this step, close() in tcp_flow_migrate_source_ext()
> > > +	 * *sometimes* closes the connection for real.
> > > +	 */
> > > +/*	{
> > > +		.name = "shrink TCP windows",
> > > +		.source = flow_migrate_source_early,
> > > +		.target = NULL,
> > > +	},
> > > +*/    
> > 
> > Given we're not sure if this will help, and it adds some
> > complications, probably makes sense to split this into a separate
> > patch.  
> 
> I'd rather not because, due to this, the code for the case *without it*
> is a bit different anyway, and we avoid some code churn. I would also
> like to merge it unused to make our lives a bit easier the day we retry
> to work on it.

Oh, I missed the fact you already split this out in v14... fine then.
There are some stray FIXMEs in 11/14, tcp_flow_migrate_source_ext():

+	/* FIXME: Reenable dump in tcp_flow_migrate_shrink_window() */

+	/* FIXME: it's either this or flow_migrate_source_early(), why? */

but I'll just drop them in the next version.

-- 
Stefano


  reply	other threads:[~2025-02-10 15:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-09 22:19 [PATCH v13 0/6] State migration, kind of draft again Stefano Brivio
2025-02-09 22:20 ` [PATCH v13 1/6] migrate: Skeleton of live migration logic Stefano Brivio
2025-02-10  2:26   ` David Gibson
2025-02-09 22:20 ` [PATCH v13 2/6] migrate: Migrate guest observed addresses Stefano Brivio
2025-02-09 22:20 ` [PATCH v13 3/6] Add interfaces and configuration bits for passt-repair Stefano Brivio
2025-02-10  2:59   ` David Gibson
2025-02-10 15:54     ` Stefano Brivio
2025-02-09 22:20 ` [PATCH v13 4/6] vhost_user: Make source quit after reporting migration state Stefano Brivio
2025-02-10  3:43   ` David Gibson
2025-02-09 22:20 ` [PATCH v13 5/6] migrate: Migrate TCP flows Stefano Brivio
2025-02-10  6:05   ` David Gibson
2025-02-10  9:51     ` Stefano Brivio
2025-02-10 15:54       ` Stefano Brivio [this message]
2025-02-09 22:20 ` [PATCH v13 6/6] test: Add migration tests Stefano Brivio

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=20250210165437.0defc859@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --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).