From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 1/3] conf: Introduce --no-bindtodevice option for testing
Date: Tue, 13 Jan 2026 23:13:20 +0100 [thread overview]
Message-ID: <20260113231320.7d9781c2@elisabeth> (raw)
In-Reply-To: <aWW1Qrn-rb9I9aY9@zatzit>
On Tue, 13 Jan 2026 14:00:18 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Tue, Jan 13, 2026 at 01:12:01AM +0100, Stefano Brivio wrote:
> > On Mon, 12 Jan 2026 14:42:39 +1100
> > David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> > > On Sun, Jan 11, 2026 at 12:33:14AM +0100, Stefano Brivio wrote:
> > >
> > > > I never really understood the point of --no-splice, as there was no
> > > > user request whatsoever behind it, but fine, the argument was that it
> > > > added some needed functionality, even though I couldn't quite grasp
> > > > which one it was.
> > >
> > > That was never the argument from _me_ for --no-splice. For me it was
> > > always that it was useful for development / testing / debugging, not
> > > that it was (directly) useful to end users.
> >
> > Right, I think Jon meant it was useful to end users. Otherwise, I would
> > have argued, it should be mentioned in the man page, and, I would have
> > argued further, the option shouldn't exist at all.
> >
> > > That's true in at least
> > > two ways:
> > > * Allows testing non-splice functionality without having to either
> > > use passt or create some non-loopback addresses
> >
> > ...but without a loopback address we can't use the tap path anyway.
>
> I'm not sure what you mean here.
Oops, I meant to say "without a loopback address you can't use the
spliced path anyway".
> If I want to exercise something on
> the tap path I can use:
> $ pasta --no-splice [whatever else]
> [...]
> $ socat STDIO TCP:localhost:12345
>
> and I don't need to look up my host's current global IP.
Ah, right, sorry! That's the bit of functionality it actually adds. I
keep forgetting about it. This wasn't possible before.
--
Stefano
next prev parent reply other threads:[~2026-01-13 22:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 8:28 [PATCH 0/3] Allow listen functions to return fds David Gibson
2026-01-05 8:28 ` [PATCH 1/3] conf: Introduce --no-bindtodevice option for testing David Gibson
2026-01-10 23:33 ` Stefano Brivio
2026-01-12 3:42 ` David Gibson
2026-01-13 0:12 ` Stefano Brivio
2026-01-13 3:00 ` David Gibson
2026-01-13 22:13 ` Stefano Brivio [this message]
2026-01-05 8:28 ` [PATCH 2/3] tcp, udp, conf: Don't silently ignore listens on unsupported IP versions David Gibson
2026-01-10 23:33 ` Stefano Brivio
2026-01-12 3:48 ` David Gibson
2026-01-13 0:12 ` Stefano Brivio
2026-01-13 3:05 ` David Gibson
2026-01-05 8:28 ` [PATCH 3/3] tcp, udp: Make {tcp,udp}_listen() return socket fds David Gibson
2026-01-10 23:33 ` Stefano Brivio
2026-01-12 3:50 ` 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=20260113231320.7d9781c2@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).