public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/5] RFC: Assorted migration improvements
Date: Fri, 31 Jan 2025 17:24:34 +1100	[thread overview]
Message-ID: <Z5xsol9JxQZUiLD9@zatzit> (raw)
In-Reply-To: <20250131064625.4ba8a099@elisabeth>

[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]

On Fri, Jan 31, 2025 at 06:46:25AM +0100, Stefano Brivio wrote:
> On Thu, 30 Jan 2025 19:55:11 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > On Thu, Jan 30, 2025 at 09:46:19AM +0100, Stefano Brivio wrote:
> > > On Thu, 30 Jan 2025 19:33:25 +1100
> > > David Gibson <david@gibson.dropbear.id.au> wrote:
> > >   
> > > > Here are some things that I think improve the draft migration logic.
> > > > This is based on both the draft migration series (v2) and my
> > > > epoll_del() series.
> > > > 
> > > > Feel free to fold into the existing patches if that seems sensible.  
> > > 
> > > Sure, let me post a v3 with these included.
> > > 
> > > Do you prefer to keep all the patches as they are or should I merge 2/5
> > > and 3/5 with the patches in my current series?  
> > 
> > Whichever you prefer.  And 1/5 probably _should_ be folded in.
> 
> So, yeah, I have a merged series ready, but I'm trying to solve the
> concrete problem I'm facing before posting it.
> 
> Actually, merging clean-ups with no _intended_ impact on functionality,
> while trying to do this, isn't terribly helpful, but it didn't take
> that long.

So, the cleanups aren't purely cleanups for the sake of cleanups:
they're things I think I need in preparation for the more compact flow
table representation stuff.

-- 
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 --]

      reply	other threads:[~2025-01-31  6:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30  8:33 [PATCH 0/5] RFC: Assorted migration improvements David Gibson
2025-01-30  8:33 ` [PATCH 1/5] migrate: Add passt-repair to .gitignore David Gibson
2025-01-30  8:33 ` [PATCH 2/5] migrate: vu_migrate_{source,target}() aren't actually vu speciic David Gibson
2025-01-30  8:33 ` [PATCH 3/5] migrate: Move repair_sock_init() to vu_init() David Gibson
2025-01-30  8:33 ` [PATCH 4/5] migrate: Make more handling common rather than vhost-user specific David Gibson
2025-01-30  8:33 ` [PATCH 5/5] migrate: Don't handle the migration channel through epoll David Gibson
2025-01-31  5:37   ` Stefano Brivio
2025-01-31  6:23     ` David Gibson
2025-01-30  8:46 ` [PATCH 0/5] RFC: Assorted migration improvements Stefano Brivio
2025-01-30  8:55   ` David Gibson
2025-01-31  5:46     ` Stefano Brivio
2025-01-31  6:24       ` David Gibson [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=Z5xsol9JxQZUiLD9@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).