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/6] Introduce unified flow table, first steps
Date: Thu, 23 Nov 2023 13:36:23 +1100	[thread overview]
Message-ID: <20231123023629.2024938-1-david@gibson.dropbear.id.au> (raw)

Here's my latest revision of some of the basics of the flow table.  So
far it's basically just a renaming of the existing TCP connection
table.  It's used for some new logging helpers, but otherwise doesn't
really function any differently.

However, this subset of the flow table work no longer bloats
flow/connection entries over a single cache line.  That removes the
most prominent drawback of earlier revisions, meaning I think this
series is ready for merge now.  Doing so will mean the later series
making more substantive changes to the flow behaviour are simpler.

David Gibson (6):
  test: Make handling of shell prompts with escapes a little more
    reliable
  flow, tcp: Generalise connection types
  flow, tcp: Move TCP connection table to unified flow table
  flow, tcp: Consolidate flow pointer<->index helpers
  flow: Make unified version of flow table compaction
  flow, tcp: Add logging helpers for connection related messages

 Makefile      |  14 +--
 flow.c        |  87 +++++++++++++++++++
 flow.h        |  60 +++++++++++++
 flow_table.h  |  45 ++++++++++
 passt.h       |   3 +
 tcp.c         | 232 +++++++++++++++++++++++---------------------------
 tcp.h         |   5 --
 tcp_conn.h    |  46 +++-------
 tcp_splice.c  |  88 +++++++++----------
 test/lib/term |   6 +-
 10 files changed, 361 insertions(+), 225 deletions(-)
 create mode 100644 flow.c
 create mode 100644 flow.h
 create mode 100644 flow_table.h

-- 
2.42.0


             reply	other threads:[~2023-11-23  2:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  2:36 David Gibson [this message]
2023-11-23  2:36 ` [PATCH 1/6] test: Make handling of shell prompts with escapes a little more reliable David Gibson
2023-11-23  2:36 ` [PATCH 2/6] flow, tcp: Generalise connection types David Gibson
2023-11-23  2:36 ` [PATCH 3/6] flow, tcp: Move TCP connection table to unified flow table David Gibson
2023-11-23  2:36 ` [PATCH 4/6] flow, tcp: Consolidate flow pointer<->index helpers David Gibson
2023-11-23  2:36 ` [PATCH 5/6] flow: Make unified version of flow table compaction David Gibson
2023-11-23  2:36 ` [PATCH 6/6] flow, tcp: Add logging helpers for connection related messages David Gibson
2023-11-23  6:58   ` Stefano Brivio
2023-11-23 22:14     ` David Gibson
2023-11-23  4:46 ` [PATCH 0/6] Introduce unified flow table, first steps 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=20231123023629.2024938-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).