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] test: Wait for network before starting passt in two_guests setup
Date: Mon, 7 Nov 2022 19:59:36 +0100	[thread overview]
Message-ID: <20221107195936.1875b08c@elisabeth> (raw)
In-Reply-To: <20221107105106.1f667fff@elisabeth>

On Mon, 7 Nov 2022 10:51:06 +0100
Stefano Brivio <sbrivio@redhat.com> wrote:

> On Mon, 7 Nov 2022 14:21:30 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > On Fri, Nov 04, 2022 at 02:53:36AM +0100, Stefano Brivio wrote:  
> > > As pasta now configures that target network namespace with
> > > --config-net, we need to wait for addresses and routes to be actually
> > > present. Just sending netlink messages doesn't mean this is done
> > > synchronously.
> > > 
> > > A more elegant alternative, which probably makes sense regardless of
> > > this test setup, would be to query, from pasta, addresses and routes
> > > we added, and wait until they're there, before proceeding.
> > > 
> > > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>    
> > 
> > Ugly, but I see the point.
> > 
> > As you say in future I hope we can actually detect the completion of
> > interface configuration which would be useful both here and other
> > places.  
> 
> Yes... the outcome of "pasta --config-net ip address show" (compared to
> "pasta --config-net -- sh -c 'sleep 0.05; ip address show'") is a bit
> bothering.
> 
> > One other thing to consider - in the case where pasta is spawing a new
> > process, rather than attaching to an existing one, it's possibly
> > counterintuitive that the process starts before pasta has completed
> > setup.  We possibly should get the spawned thread to wait until the
> > main pasta thread is entering its main loop before exec()ing the
> > shell.  Obviously requires some sync mechanism, which is a bit clunky.  
> 
> Right, that might be a problem if somebody spawns a script that relies
> on the tap interface to be working right away (even though the delay is
> probably small enough for all practical cases).
> 
> I'll file a ticket covering both topics.

... https://bugs.passt.top/show_bug.cgi?id=37.

-- 
Stefano


      reply	other threads:[~2022-11-07 18:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  1:53 [PATCH] test: Wait for network before starting passt in two_guests setup Stefano Brivio
2022-11-07  3:21 ` David Gibson
2022-11-07  3:54   ` David Gibson
2022-11-07  9:51   ` Stefano Brivio
2022-11-07 18:59     ` 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=20221107195936.1875b08c@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).