[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZzKeCJZoEIFoiJyO@LQ3V64L9R2>
Date: Mon, 11 Nov 2024 16:15:04 -0800
From: Joe Damato <jdamato@...tly.com>
To: John Ousterhout <ouster@...stanford.edu>
Cc: netdev@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: [PATCH net-next v2 00/12] Begin upstreaming Homa transport
protocol
On Mon, Nov 11, 2024 at 03:39:53PM -0800, 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.
Quick note for future versions:
Consider adding a changelog to the cover letter and to the
individual patches which change from revision to revision to make
it easier for folks to follow along with what changed.
You can find more information about this here:
https://www.kernel.org/doc/html/v6.11/process/submitting-patches.html#respond-to-review-comments
And it might be helpful to take a look at other series on the list
which have multiple revisions [1] to get a sense of how others
typically do this.
[1]: https://lore.kernel.org/netdev/20241030-feature_ptp_netnext-v19-0-94f8aadc9d5c@bootlin.com/
Powered by blists - more mailing lists