From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/4] Passt Interface Identifiers
Date: Mon, 9 Oct 2023 19:30:09 +1100 [thread overview]
Message-ID: <20231009083013.2837178-1-david@gibson.dropbear.id.au> (raw)
For the generalisations to forwarding we want to accomplish with the
flow table, we will need a more formalised notion of passt
"interfaces" - that is way that passt communicates with network,
whether that be over L4 sockets (as on the host) or via an L2 tunnel.
This series makes a small start on this, by introducing a type to
identify passt interfaces. We don't use it for a whole lot yet, but
it will become more useful in future.
David Gibson (4):
udp: Clean up ref initialisation in udp_sock_init()
pif: Introduce notion of passt/pasta interface
pif: Record originating pif in listening socket refs
pif: Pass originating pif to tap handler functions
Makefile | 2 +-
icmp.c | 4 +++-
icmp.h | 4 ++--
passt.h | 1 +
pif.h | 36 ++++++++++++++++++++++++++++++++++++
tap.c | 26 ++++++++++++++++----------
tcp.c | 11 ++++++++---
tcp.h | 7 ++++---
tcp_splice.c | 10 ++++++----
udp.c | 35 ++++++++++++++++++-----------------
udp.h | 11 ++++++-----
11 files changed, 101 insertions(+), 46 deletions(-)
create mode 100644 pif.h
--
2.41.0
next reply other threads:[~2023-10-09 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 8:30 David Gibson [this message]
2023-10-09 8:30 ` [PATCH 1/4] udp: Clean up ref initialisation in udp_sock_init() David Gibson
2023-10-09 8:30 ` [PATCH 2/4] pif: Introduce notion of passt/pasta interface David Gibson
2023-10-09 8:30 ` [PATCH 3/4] pif: Record originating pif in listening socket refs David Gibson
2023-11-03 9:47 ` Stefano Brivio
2023-11-04 2:03 ` David Gibson
2023-10-09 8:30 ` [PATCH 4/4] pif: Pass originating pif to tap handler functions 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=20231009083013.2837178-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).