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/4] RFC: Some cleanups to tap and tcp
Date: Fri, 27 Jan 2023 16:11:06 +1100 [thread overview]
Message-ID: <20230127051110.2513363-1-david@gibson.dropbear.id.au> (raw)
This is a handful of simple cleanups which I made while investigating
https://bugs.passt.top/show_bug.cgi?id=41. Note that these don't
themselves actually address that bug, they're just unrelated cleanups
that happen to be in adjacent code.
These are barely tested at all. I've had some crises right before
going away that mean I haven't had a chance to plish these. I'm
posting them so they're out there rather than waiting until I'm back
in two weeks.
These are based on my tap send unification series and the TCP socket
pool cleanup series.
David Gibson (4):
tap: Don't pcap frames that didn't get sent
tap: Eliminate goto from tap_handler()
tcp: Remove 'recvmsg' goto from tcp_data_from_sock
tcp: Remove 'zero_len' goto from tcp_data_from_sock
tap.c | 49 +++++++++++++++++++++++++++----------------------
tcp.c | 37 +++++++++++++++++--------------------
2 files changed, 44 insertions(+), 42 deletions(-)
--
2.39.1
next reply other threads:[~2023-01-27 5:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 5:11 David Gibson [this message]
2023-01-27 5:11 ` [PATCH 1/4] tap: Don't pcap frames that didn't get sent David Gibson
2023-02-15 12:17 ` Stefano Brivio
2023-02-16 5:20 ` David Gibson
2023-02-16 7:43 ` Stefano Brivio
2023-01-27 5:11 ` [PATCH 2/4] tap: Eliminate goto from tap_handler() David Gibson
2023-01-27 5:11 ` [PATCH 3/4] tcp: Remove 'recvmsg' goto from tcp_data_from_sock David Gibson
2023-02-15 12:17 ` Stefano Brivio
2023-02-16 0:28 ` David Gibson
2023-01-27 5:11 ` [PATCH 4/4] tcp: Remove 'zero_len' " 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=20230127051110.2513363-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).