From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/5] RFC: Stub dynamic update implementation
Date: Mon, 16 Mar 2026 16:46:24 +1100 [thread overview]
Message-ID: <20260316054629.239002-1-david@gibson.dropbear.id.au> (raw)
I've taken Stefano's draft implementation of dynamic updates, and
polished it up to have a stub implementation of the dynamic update
protocol. So far it doesn't actually do anything, beyond establishing
the connection and checking versions. I'm continuing to work on the
actual guts of it.
Patches 1..3/5 are trivial cleanups I happened across while working on
this. Feel free to apply if you like. 4/5 clears up a more specific
problem that caused problems sharing code between client and server.
5/5 is the implementation proper.
David Gibson (5):
Makefile: Use $^ to avoid duplication in static checker rules
doc: Fix formatting of (DEPRECATED) notes in man page
pif: Remove unused PIF_NAMELEN
treewide: Spell ASSERT() as assert()
pesto: Introduce stub configuration interface and tool
.gitignore | 2 +
Makefile | 36 +++++++-----
conf.c | 154 +++++++++++++++++++++++++++++++++++++++++++++++++--
conf.h | 2 +
epoll_type.h | 4 ++
flow.c | 80 +++++++++++++-------------
flow_table.h | 2 +-
fwd.c | 14 ++---
icmp.c | 14 ++---
inany.h | 4 +-
iov.c | 2 +-
isolation.c | 2 +-
lineread.c | 4 +-
netlink.c | 2 +-
packet.c | 4 +-
passt.1 | 9 ++-
passt.c | 10 +++-
passt.h | 6 ++
pesto.1 | 47 ++++++++++++++++
pesto.c | 111 +++++++++++++++++++++++++++++++++++++
pesto.h | 34 ++++++++++++
pesto_util.c | 62 +++++++++++++++++++++
pesto_util.h | 19 +++++++
pif.c | 4 +-
pif.h | 2 -
tap.c | 6 +-
tcp.c | 24 ++++----
tcp_splice.c | 10 ++--
tcp_vu.c | 8 +--
udp.c | 22 ++++----
udp_flow.c | 4 +-
udp_vu.c | 4 +-
util.c | 42 +-------------
util.h | 15 ++---
vhost_user.c | 8 +--
virtio.c | 4 +-
vu_common.c | 4 +-
37 files changed, 599 insertions(+), 182 deletions(-)
create mode 100644 pesto.1
create mode 100644 pesto.c
create mode 100644 pesto.h
create mode 100644 pesto_util.c
create mode 100644 pesto_util.h
--
2.53.0
next reply other threads:[~2026-03-16 5:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 5:46 David Gibson [this message]
2026-03-16 5:46 ` [PATCH 1/5] Makefile: Use $^ to avoid duplication in static checker rules David Gibson
2026-03-16 5:46 ` [PATCH 2/5] doc: Fix formatting of (DEPRECATED) notes in man page David Gibson
2026-03-16 5:46 ` [PATCH 3/5] pif: Remove unused PIF_NAMELEN David Gibson
2026-03-16 5:46 ` [PATCH 4/5] treewide: Spell ASSERT() as assert() David Gibson
2026-03-17 0:02 ` Stefano Brivio
2026-03-17 0:39 ` David Gibson
2026-03-17 9:36 ` Stefano Brivio
2026-03-16 5:46 ` [PATCH 5/5] pesto: Introduce stub configuration interface and tool David Gibson
2026-03-17 0:02 ` Stefano Brivio
2026-03-17 0:48 ` David Gibson
2026-03-17 9:36 ` Stefano Brivio
2026-03-17 0:02 ` [PATCH 0/5] RFC: Stub dynamic update implementation Stefano Brivio
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=20260316054629.239002-1-david@gibson.dropbear.id.au \
--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).