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] Cleanups to packet pool handling and sizing
Date: Fri, 13 Dec 2024 23:01:53 +1100 [thread overview]
Message-ID: <20241213120156.4123972-1-david@gibson.dropbear.id.au> (raw)
This... is not any of the things I said I would be working on. I can
only say that a herd of very hairy yaks led me astray. Looking at bug
66 I spotted some problems with our handling of MTUs / maximum frame
sizes. Looking at that I found some weirdness and some real, if
minor, bugs in the sizing and handling of the packet pools.
David Gibson (3):
packet: Use flexible array member in struct pool
packet: Don't have struct pool specify its buffer
tap: Don't size pool_tap[46] for the maximum number of packets
packet.c | 63 ++++++----------------------------------------------
packet.h | 41 ++++++++++++----------------------
passt.h | 2 --
tap.c | 63 +++++++++++++++++++++++++---------------------------
tap.h | 4 ++--
vhost_user.c | 2 --
vu_common.c | 31 ++------------------------
7 files changed, 55 insertions(+), 151 deletions(-)
--
2.47.1
next reply other threads:[~2024-12-13 12:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 12:01 David Gibson [this message]
2024-12-13 12:01 ` [PATCH 1/3] packet: Use flexible array member in struct pool David Gibson
2024-12-13 12:01 ` [PATCH 2/3] packet: Don't have struct pool specify its buffer David Gibson
2024-12-19 9:00 ` Stefano Brivio
2024-12-20 0:59 ` David Gibson
2024-12-20 9:51 ` Stefano Brivio
2024-12-21 6:59 ` David Gibson
2024-12-13 12:01 ` [PATCH 3/3] tap: Don't size pool_tap[46] for the maximum number of packets David Gibson
2024-12-19 9:00 ` Stefano Brivio
2024-12-20 1:13 ` David Gibson
2024-12-20 9:51 ` Stefano Brivio
2024-12-21 7:00 ` 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=20241213120156.4123972-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).