From: Jon Maloy <jmaloy@redhat.com>
To: "passt-dev@passt.top" <passt-dev@passt.top>
Subject: PASST/PASST Dynamic Networking Features
Date: Fri, 5 Dec 2025 15:55:04 -0500 [thread overview]
Message-ID: <686640a9-f760-44a0-ad75-3b9ad20af265@redhat.com> (raw)
Hi all,
Before going further with the implementation, I spent some time to
understand the contents and implications of the various bugs/texts we
have in this area.
I then tried, to the best of my ability, to compile them into user
stories, which I think might be a good format for our users to
evaluate this.
https://pad.passt.top/p/NetlinkMonitor
Please have a look and give feedback!
///jon
reply other threads:[~2025-12-05 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=686640a9-f760-44a0-ad75-3b9ad20af265@redhat.com \
--to=jmaloy@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).