From: Stefano Brivio <sbrivio@redhat.com>
To: Jon Maloy <jmaloy@redhat.com>
Cc: passt-dev@passt.top, lvivier@redhat.com, dgibson@redhat.com
Subject: Re: [PATCH v2] pasta: make it possible to disable socket splicing
Date: Sat, 30 Nov 2024 00:57:38 +0100 [thread overview]
Message-ID: <20241130005738.19aa116f@elisabeth> (raw)
In-Reply-To: <20241129224946.2664970-1-jmaloy@redhat.com>
On Fri, 29 Nov 2024 17:49:46 -0500
Jon Maloy <jmaloy@redhat.com> wrote:
> During testing it is sometimes useful to force traffic which would
> normally be forwared by socket splicing through the tap interface.
>
> In this commit, we add a command switch enabling such funtionality
> for inbound local traffic.
>
> For outbound local traffic this is much trickier, if even possible,
> so leave that for a later commit.
>
> Suggested-by: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: Jon Maloy <jmaloy@redhat.com>
>
> ---
> v2: Some minor changes based on feedback from PASST team
> ---
> conf.c | 5 +++++
> fwd.c | 2 +-
> passt.h | 2 ++
> 3 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/conf.c b/conf.c
> index 5107549..fe6fa04 100644
> --- a/conf.c
> +++ b/conf.c
> @@ -846,6 +846,7 @@ static void usage(const char *name, FILE *f, int status)
> " --no-ndp Disable NDP responses\n"
> " --no-dhcpv6 Disable DHCPv6 server\n"
> " --no-ra Disable router advertisements\n"
> + " --no-splice Disable inbound socket splicing\n"
I think this really needs an update to the man page as David mentioned.
We don't have any undocumented option (as far as I know!) and I don't
think it would be a particularly good idea to start now...
--
Stefano
next prev parent reply other threads:[~2024-11-29 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 22:49 [PATCH v2] pasta: make it possible to disable socket splicing Jon Maloy
2024-11-29 23:57 ` Stefano Brivio [this message]
2024-12-03 3:43 ` 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=20241130005738.19aa116f@elisabeth \
--to=sbrivio@redhat.com \
--cc=dgibson@redhat.com \
--cc=jmaloy@redhat.com \
--cc=lvivier@redhat.com \
--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).