From: Jakub Kicinski <kuba@kernel.org>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
horms@kernel.org
Subject: Re: [PATCH net-next v18 00/15] Begin upstreaming Homa transport protocol
Date: Sun, 12 Apr 2026 13:45:31 -0700 [thread overview]
Message-ID: <20260412134531.21341692@kernel.org> (raw)
In-Reply-To: <20260410200310.1915-1-ouster@cs.stanford.edu>
On Fri, 10 Apr 2026 13:02:54 -0700 John Ousterhout wrote:
> This patch series begins the process of upstreaming the Homa transport
> protocol. Homa is an alternative to TCP for use in datacenter
> environments. It provides 10-100x reductions in tail latency for short
> messages relative to TCP. Its benefits are greatest for mixed workloads
> containing both short and long messages running under high network loads.
> Homa is not API-compatible with TCP: it is connectionless and message-
> oriented (but still reliable and flow-controlled). Homa's new API not
> only contributes to its performance gains, but it also eliminates the
> massive amount of connection state required by TCP for highly connected
> datacenter workloads (Homa uses ~ 1 socket per application, whereas
> TCP requires a separate socket for each peer).
make coccicheck says:
net/homa/homa_peer.c:213:21-22: WARNING opportunity for swap()
next prev parent reply other threads:[~2026-04-12 20:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 20:02 [PATCH net-next v18 00/15] Begin upstreaming Homa transport protocol John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 01/15] net: homa: define user-visible API for Homa John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 02/15] net: homa: create homa_wire.h John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 03/15] net: homa: create shared Homa header files John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 04/15] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 05/15] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 06/15] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 07/15] net: homa: create homa_interest.h and homa_interest.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 08/15] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 09/15] net: homa: create homa_outgoing.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 10/15] net: homa: create homa_utils.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 11/15] net: homa: export skb_attempt_defer_free John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 12/15] net: homa: create homa_incoming.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 13/15] net: homa: create homa_timer.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 14/15] net: homa: create homa_plumbing.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 15/15] net: homa: create Makefile and Kconfig John Ousterhout
2026-04-12 20:45 ` Jakub Kicinski [this message]
2026-04-13 23:54 ` [PATCH net-next v18 00/15] Begin upstreaming Homa transport protocol John Ousterhout
2026-04-15 23:21 ` John Ousterhout
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=20260412134531.21341692@kernel.org \
--to=kuba@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ouster@cs.stanford.edu \
--cc=pabeni@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.