Index | Thread | Search

From:
Jan Klemkow <jan@openbsd.org>
Subject:
Re: names for TSO and LRO
To:
Alexander Bluhm <bluhm@openbsd.org>
Cc:
tech@openbsd.org
Date:
Wed, 16 Apr 2025 23:59:43 +0200

Download raw body.

Thread
On Wed, Apr 16, 2025 at 11:39:21PM GMT, Alexander Bluhm wrote:
> Now that we have software LRO, we need consistent naming with TSO.
> One is called tcp_softlro and the other tcp_copper.  As claudio@
> suggested the descriptive name "copper", I would like to have it
> this way for LRO.  tcp_glue_enqueue() came to my mind.

In my opinion we should not make up new names for already established
things.  LRO und TSO are established names [1].  If you google "tcp
glue" you will very misleading results.  Looks like its a product name
for some glue.  Also "tcp copper" won't get better search results.

Thus, I suggest to rename tcp_copper() to tcp_softtso() to get things
consistent here.  Or, tcp_tso() and tcp_lro() to keep it shorter.

[1]: https://en.wikipedia.org/wiki/TCP_offload_engine