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 v3 4/4] fwd: Direct inbound spliced forwards to the guest's external address
Date: Thu, 17 Oct 2024 16:06:29 +1100	[thread overview]
Message-ID: <ZxCbVSpSus2BxC_D@zatzit.fritz.box> (raw)
In-Reply-To: <20241016172648.666b0f8c@elisabeth>

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

On Wed, Oct 16, 2024 at 05:26:48PM +0200, Stefano Brivio wrote:
[snip]
> Adding 2-second delays as we have them for NDP doesn't look that bad:

> $ grep --exclude-dir=demo -rn "dhclient -6" pasta/dhcp:37:ns
> /sbin/dhclient -6 --no-pid __IFNAME__ passt_in_ns/dhcp:54:guest
> /sbin/dhclient -6 __IFNAME__ passt/dhcp:51:guest /sbin/dhclient -6
> __IFNAME__ perf/passt_tcp:117:guest dhclient -6 -x
> perf/passt_tcp:118:guest dhclient -6 __IFNAME__
> two_guests/basic:40:guest1 /sbin/dhclient -6 __IFNAME1__
> two_guests/basic:41:guest2 /sbin/dhclient -6 __IFNAME2__

> given that we don't need it on dhclient -x, tests would take about
> 12 seconds longer.

> Or we could switch to the arp off / nodad / arp on approach for
> everything, including SLAAC:

> $ grep --exclude-dir=demo --exclude-dir=mbuto --exclude-dir=distro
> --exclude-dir=memory -rn "sleep[ $(printf '\t')].*2"
> pasta/ndp:21:sleep 2 passt_in_ns/icmp:29:ns ip addr add 2001:db8::1
> dev __IFNAME_NS__ && sleep 2 # DAD passt/ndp:19:guest ip link set
> dev __IFNAME__ up && sleep 2 two_guests/basic:39:sleep 2

> and save slightly less than 8 seconds. If you ask me, I would have a
> slight preference for the nodad approach.

Much as I don't like making the tests slower, I don't think the nodad
approach is a good idea.  It's fine if we think of the NDP/DHCP only
as setting things up for the transfer tests.  But they also serve the
purpose of testing the NDP and DHCP paths themselves.  For that
purpose we should perform a full "normal" configuration, including
DAD.  [e.g. if we really did manage to break our NS responses so that
we totally broke DAD, we'd want our tests to catch that].

I have a draft implementation of explicitly waiting for DAD to
complete both for SLAAC and for DHCPv6, patches coming shortly.

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

      parent reply	other threads:[~2024-10-17  5:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02  5:48 [PATCH v3 0/4] Don't expose container loopback services to the host David Gibson
2024-10-02  5:48 ` [PATCH v3 1/4] passt.1: Mark --stderr as deprecated more prominently David Gibson
2024-10-02  5:48 ` [PATCH v3 2/4] passt.1: Clarify and update "Handling of local addresses" section David Gibson
2024-10-02  5:48 ` [PATCH v3 3/4] test: Clarify test for spliced inbound transfers David Gibson
2024-10-02  5:48 ` [PATCH v3 4/4] fwd: Direct inbound spliced forwards to the guest's external address David Gibson
2024-10-09 13:07   ` Stefano Brivio
2024-10-09 20:44     ` Stefano Brivio
2024-10-10  5:57       ` David Gibson
2024-10-16  3:15         ` David Gibson
2024-10-16  5:46           ` David Gibson
2024-10-16  8:39             ` David Gibson
2024-10-16 15:26               ` Stefano Brivio
2024-10-17  1:19                 ` David Gibson
2024-10-17  8:31                   ` Stefano Brivio
2024-10-21  1:35                     ` David Gibson
2024-10-17  5:06                 ` 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=ZxCbVSpSus2BxC_D@zatzit.fritz.box \
    --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).