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/3] RFC: TCP hash change changes, in preparation for flow table
Date: Mon, 4 Dec 2023 14:16:08 +1100 [thread overview]
Message-ID: <20231204031611.3566791-1-david@gibson.dropbear.id.au> (raw)
I now have an in-progress draft of a unified hash table to go with the
unified flow table. This turns out to be easier if we first make some
preliminary changes to the structure of the TCP hash table. So, here
those are for review.
This is based on my already posted series introducing the rudimentary
version of the unified flow table.
David Gibson (3):
tcp: Switch hash table to linear probing instead of chaining
tcp: Implement hash table with indices rather than pointers
tcp: Don't account for hash table size in tcp_hash()
flow.h | 11 ++++
tcp.c | 144 ++++++++++++++++++++++++++++-------------------------
tcp_conn.h | 2 -
util.h | 13 +++++
4 files changed, 101 insertions(+), 69 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-04 3:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 3:16 David Gibson [this message]
2023-12-04 3:16 ` [PATCH 1/3] tcp: Switch hash table to linear probing instead of chaining David Gibson
2023-12-06 22:43 ` Stefano Brivio
2023-12-07 4:11 ` David Gibson
2023-12-11 9:00 ` Stefano Brivio
2023-12-04 3:16 ` [PATCH 2/3] tcp: Implement hash table with indices rather than pointers David Gibson
2023-12-06 19:37 ` Stefano Brivio
2023-12-07 1:04 ` David Gibson
2023-12-07 5:10 ` David Gibson
2023-12-07 6:20 ` Stefano Brivio
2023-12-04 3:16 ` [PATCH 3/3] tcp: Don't account for hash table size in tcp_hash() 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=20231204031611.3566791-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).