public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
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/3] Basic integration of ICMP with flow table
Date: Thu, 29 Feb 2024 15:15:31 +1100	[thread overview]
Message-ID: <20240229041534.2573559-1-david@gibson.dropbear.id.au> (raw)

I realized that even with the rudimentary form of the flow table we
have now, it's possible to integrate ICMP (ping).  This even
simplifies a little bit of logic in the ICMP code.

This is based on the address handling clean up series.

David Gibson (3):
  icmp: Store ping socket information in flow table
  icmp: Flow based error reporting
  icmp: Use 'flowside' epoll references for ping sockets

 Makefile     |   6 +-
 flow.c       |   9 +++
 flow.h       |   4 ++
 flow_table.h |   2 +
 icmp.c       | 194 +++++++++++++++++++++++----------------------------
 icmp.h       |  15 +---
 icmp_flow.h  |  31 ++++++++
 passt.c      |  15 +---
 passt.h      |   7 +-
 util.c       |   4 +-
 10 files changed, 146 insertions(+), 141 deletions(-)
 create mode 100644 icmp_flow.h

-- 
2.44.0


             reply	other threads:[~2024-02-29  4:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  4:15 David Gibson [this message]
2024-02-29  4:15 ` [PATCH 1/3] icmp: Store ping socket information in flow table David Gibson
2024-03-07  8:53   ` Stefano Brivio
2024-03-07 10:24     ` David Gibson
2024-03-07 23:25       ` Stefano Brivio
2024-03-08  0:48         ` David Gibson
2024-02-29  4:15 ` [PATCH 2/3] icmp: Flow based error reporting David Gibson
2024-03-07 23:26   ` Stefano Brivio
2024-03-08  0:49     ` David Gibson
2024-03-08  6:06       ` Stefano Brivio
2024-02-29  4:15 ` [PATCH 3/3] icmp: Use 'flowside' epoll references for ping sockets David Gibson
2024-03-13 10:08 ` [PATCH 0/3] Basic integration of ICMP with flow table 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=20240229041534.2573559-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).