public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 0/4] Passt Interface Identifiers
Date: Tue, 7 Nov 2023 13:45:11 +0100	[thread overview]
Message-ID: <20231107134511.4e4c8e93@elisabeth> (raw)
In-Reply-To: <20231107014016.1927410-1-david@gibson.dropbear.id.au>

On Tue,  7 Nov 2023 12:40:12 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> 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.
> 
> Based on the automatic port forwarding cleanup series
> 
> Changes since v1:
>  * Don't use a type alias for pif ids, just use bare uint8_t
> 
> 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

Applied.

-- 
Stefano


      parent reply	other threads:[~2023-11-07 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07  1:40 [PATCH v2 0/4] Passt Interface Identifiers David Gibson
2023-11-07  1:40 ` [PATCH v2 1/4] udp: Clean up ref initialisation in udp_sock_init() David Gibson
2023-11-07  1:40 ` [PATCH v2 2/4] pif: Introduce notion of passt/pasta interface David Gibson
2023-11-07  1:40 ` [PATCH v2 3/4] pif: Record originating pif in listening socket refs David Gibson
2023-11-07  1:40 ` [PATCH v2 4/4] pif: Pass originating pif to tap handler functions David Gibson
2023-11-07 12:45 ` Stefano Brivio [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=20231107134511.4e4c8e93@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --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).