From: John Ousterhout <ouster@cs.stanford.edu>
To: netdev@vger.kernel.org
Cc: pabeni@redhat.com, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, John Ousterhout <ouster@cs.stanford.edu>
Subject: [PATCH net-next v16 14/14] net: homa: create Makefile and Kconfig
Date: Wed, 15 Oct 2025 11:51:01 -0700 [thread overview]
Message-ID: <20251015185102.2444-15-ouster@cs.stanford.edu> (raw)
In-Reply-To: <20251015185102.2444-1-ouster@cs.stanford.edu>
Before this commit the Homa code is "inert": it won't be compiled
in kernel builds. This commit adds Homa's Makefile and Kconfig, and
also links Homa into net/Makefile and net/Kconfig, so that Homa
will be built during kernel builds if enabled (it is disabled by
default).
Signed-off-by: John Ousterhout <ouster@cs.stanford.edu>
---
net/homa/Kconfig | 21 +++++++++++++++++++++
net/homa/Makefile | 11 +++++++++++
2 files changed, 32 insertions(+)
create mode 100644 net/homa/Kconfig
create mode 100644 net/homa/Makefile
diff --git a/net/homa/Kconfig b/net/homa/Kconfig
new file mode 100644
index 000000000000..16fec3fd52ba
--- /dev/null
+++ b/net/homa/Kconfig
@@ -0,0 +1,21 @@
+# SPDX-License-Identifier: BSD-2-Clause or GPL-2.0+
+#
+# Homa transport protocol
+#
+
+menuconfig HOMA
+ tristate "The Homa transport protocol"
+ depends on INET
+ depends on IPV6
+
+ help
+ Homa is a network transport protocol for communication within
+ a datacenter. It provides significantly lower latency than TCP,
+ particularly for workloads containing a mixture of large and small
+ messages operating at high network utilization. At present, Homa
+ has been only partially upstreamed; this version provides bare-bones
+ functionality but is not performant. For more information see the
+ homa(7) man page or checkout the Homa Wiki at
+ https://homa-transport.atlassian.net/wiki/spaces/HOMA/overview.
+
+ If unsure, say N.
diff --git a/net/homa/Makefile b/net/homa/Makefile
new file mode 100644
index 000000000000..57f051d44c6b
--- /dev/null
+++ b/net/homa/Makefile
@@ -0,0 +1,11 @@
+obj-$(CONFIG_HOMA) := homa.o
+homa-y:= homa_incoming.o \
+ homa_interest.o \
+ homa_outgoing.o \
+ homa_peer.o \
+ homa_plumbing.o \
+ homa_pool.o \
+ homa_rpc.o \
+ homa_sock.o \
+ homa_timer.o \
+ homa_utils.o
--
2.43.0
prev parent reply other threads:[~2025-10-15 18:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 18:50 [PATCH net-next v16 00/14] Begin upstreaming Homa transport protocol John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 01/14] net: homa: define user-visible API for Homa John Ousterhout
2025-10-27 9:37 ` Simon Horman
2025-10-27 15:25 ` John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 02/14] net: homa: create homa_wire.h John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 03/14] net: homa: create shared Homa header files John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 04/14] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 05/14] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 06/14] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 07/14] net: homa: create homa_interest.h and homa_interest.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 08/14] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 09/14] net: homa: create homa_outgoing.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 10/14] net: homa: create homa_utils.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 11/14] net: homa: create homa_incoming.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 12/14] net: homa: create homa_timer.c John Ousterhout
2025-10-15 18:51 ` [PATCH net-next v16 13/14] net: homa: create homa_plumbing.c John Ousterhout
2025-10-15 18:51 ` John Ousterhout [this message]
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=20251015185102.2444-15-ouster@cs.stanford.edu \
--to=ouster@cs.stanford.edu \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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 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 NNTP newsgroup(s).