From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 04/11] udp: Rename IOV and mmsghdr arrays
Date: Thu, 4 Jul 2024 23:20:53 +0200 [thread overview]
Message-ID: <20240704232053.2e7c735d@elisabeth> (raw)
In-Reply-To: <20240704045835.1149746-5-david@gibson.dropbear.id.au>
On Thu, 4 Jul 2024 14:58:28 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> Make the salient points about these various arrays clearer with renames:
>
> * udp_l2_iov_sock and udp[46]_l2_mh_sock don't really have anything to do
> with L2.
The original idea behind that 'l2' there was to have the type of
destination in the name first, and then the source ('sock').
On the other hand, they're actually clearer this way.
> They are, however, specific to receiving not sending not receiving.
I failed to decrypt this one. :)
> Rename to udp_iov_recv and udp[46]_mh_recv.
>
> * udp[46]_l2_iov_tap is redundant - "tap" implies L2 and vice versa.
> Rename to udp[46]_l2_iov
>
> * udp[46]_localname are (for now) pre-populated with the locan address
> but the more salient point is that these are the destination address for
> the splice arrays. Rename to udp[46]_spliceto
Very slight preference (but not worth a lot of changes, in case):
udp[46]_splice_to. To me it's not immediately obvious those are two
words otherwise.
--
Stefano
next prev parent reply other threads:[~2024-07-04 21:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 4:58 [PATCH 00/11] Preliminaries for UDP flow support David Gibson
2024-07-04 4:58 ` [PATCH 01/11] util: sock_l4() determine protocol from epoll type rather than the reverse David Gibson
2024-07-04 21:19 ` Stefano Brivio
2024-07-04 23:51 ` David Gibson
2024-07-04 4:58 ` [PATCH 02/11] flow: Add flow_sidx_valid() helper David Gibson
2024-07-04 4:58 ` [PATCH 03/11] udp: Pass full epoll reference through more of sock handler path David Gibson
2024-07-04 21:20 ` Stefano Brivio
2024-07-04 23:54 ` David Gibson
2024-07-04 4:58 ` [PATCH 04/11] udp: Rename IOV and mmsghdr arrays David Gibson
2024-07-04 21:20 ` Stefano Brivio [this message]
2024-07-05 0:00 ` David Gibson
2024-07-04 4:58 ` [PATCH 05/11] udp: Unify udp[46]_mh_splice David Gibson
2024-07-04 4:58 ` [PATCH 06/11] udp: Unify udp[46]_l2_iov David Gibson
2024-07-04 4:58 ` [PATCH 07/11] udp: Don't repeatedly initialise udp[46]_eth_hdr David Gibson
2024-07-04 4:58 ` [PATCH 08/11] udp: Move some more of sock_handler tasks into sub-functions David Gibson
2024-07-04 4:58 ` [PATCH 09/11] udp: Consolidate datagram batching David Gibson
2024-07-05 9:10 ` Stefano Brivio
2024-07-05 9:36 ` David Gibson
2024-07-04 4:58 ` [PATCH 10/11] contrib: Add program to document and test assumptions about SO_REUSEADDR David Gibson
2024-07-04 21:21 ` Stefano Brivio
2024-07-05 0:06 ` David Gibson
2024-07-05 8:33 ` Stefano Brivio
2024-07-05 9:49 ` David Gibson
2024-07-04 4:58 ` [PATCH 11/11] contrib: Test behaviour of zero length datagram recv()s 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=20240704232053.2e7c735d@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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).