From: Laurent Vivier <lvivier@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH] net: update netdev stream/dgram man page
Date: Tue, 2 Jul 2024 10:19:52 +0200 [thread overview]
Message-ID: <8e453d30-1bdd-4c6e-af00-0b3c115e9daf@redhat.com> (raw)
In-Reply-To: <CAJ+F1C+1fmOfE_48iNxCRvxNB+Q_yBrJAUoAi7WyPx-=N756-g@mail.gmail.com>
On 02/07/2024 10:08, Marc-André Lureau wrote:
> Hi
>
> On Wed, Jun 26, 2024 at 7:53 PM Laurent Vivier <lvivier@redhat.com
> <mailto:lvivier@redhat.com>> wrote:
>
> Add the description of "-netdev stream" and "-netdev dgram" in the QEMU
> manpage.
>
> Add some examples on how to use them, including a way to use
> "-netdev stream" and "passt" in place of "-netdev user".
> ("passt" is a non privileged translation proxy between layer-2,
> like "-netdev stream", and layer-4 on host, like TCP, UDP,
> ICMP/ICMPv6 echo)
>
>
> Was there any plan to have passt fallback (default / "-net passt") when slirp is disabled
> ? spawning the process with -F fd etc. That would help migrating away from slirp for some
> systems.
Yes, I'm planning to add a "-netdev passt" that will start passt and connect it to a
stream socket to QEMU. Perhaps at some point we can have a "-netdev slirp" and "-netdev
user" will us by default passt?
I'm also working on a vhost-user interface for passt that will also improve performance of
user mode networking with QEMU.
Thanks,
Laurent
prev parent reply other threads:[~2024-07-02 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:51 [PATCH] net: update netdev stream/dgram man page Laurent Vivier
2024-07-02 7:39 ` Marc-André Lureau
2024-07-04 7:46 ` Laurent Vivier
2024-07-02 8:08 ` Marc-André Lureau
2024-07-02 8:19 ` Laurent Vivier [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=8e453d30-1bdd-4c6e-af00-0b3c115e9daf@redhat.com \
--to=lvivier@redhat.com \
--cc=jasowang@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
/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.
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 NNTP newsgroup(s).