From: Simon Horman <horms@kernel.org>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
kuba@kernel.org
Subject: Re: [PATCH net-next v9 03/15] net: homa: create shared Homa header files
Date: Fri, 13 Jun 2025 15:40:55 +0100 [thread overview]
Message-ID: <20250613144055.GI414686@horms.kernel.org> (raw)
In-Reply-To: <20250609154051.1319-4-ouster@cs.stanford.edu>
On Mon, Jun 09, 2025 at 08:40:36AM -0700, John Ousterhout wrote:
> homa_impl.h defines "struct homa", which contains overall information
> about the Homa transport, plus various odds and ends that are used
> throughout the Homa implementation.
>
> homa_stub.h is a temporary header file that provides stubs for
> facilities that have omitted for this first patch series. This file
> will go away once Home is fully upstreamed.
>
> Signed-off-by: John Ousterhout <ouster@cs.stanford.edu>
>
> ---
> Changes for v9:
> * Move information from sync.txt into comments in homa_impl.h
> * Add limits on number of active peer structs
> * Introduce homa_net objects; there is now a single global struct homa
> shared by all network namespaces, with one homa_net per network namespace
> with netns-specific information.
> * Introduce homa_clock as an abstraction layer for the fine-grain clock.
> * Various name improvements (e.g. use "alloc" instead of "new" for functions
> that allocate memory)
> * Eliminate sizeof32 definition
>
> Changes for v8:
> * Pull out pacer-related fields into separate struct homa_pacer in homa_pacer.h
>
> Changes for v7:
> * Make Homa a per-net subsystem
> * Track tx buffer memory usage
> * Refactor waiting mechanism for incoming packets: simplify wait
> criteria and use standard Linux mechanisms for waiting
> * Remove "lock_slow" functions, which don't add functionality in this
> patch series
> * Rename homa_rpc_free to homa_rpc_end
> * Add homa_make_header_avl function
> * Use u64 and __u64 properly
> ---
> net/homa/homa_impl.h | 603 +++++++++++++++++++++++++++++++++++++++++++
> net/homa/homa_stub.h | 91 +++++++
> 2 files changed, 694 insertions(+)
> create mode 100644 net/homa/homa_impl.h
> create mode 100644 net/homa/homa_stub.h
>
> diff --git a/net/homa/homa_impl.h b/net/homa/homa_impl.h
...
> +#ifdef __CHECKER__
> +#define __context__(x, y, z) __attribute__((context(x, y, z)))
> +#else
> +#define __context__(...)
> +#endif /* __CHECKER__ */
I am unclear on the intent of this. But it does seem to be an
unusual approach within the Kernel (I couldn't find any other similar
code in-tree. And, with other patches in this series, it does seem
to lead to Sparse and Smatch flagging the following (and other similar
warnings):
.../rhashtable.h:411:9: error: macro "__context__" requires 3 arguments, but only 2 given
.../rhashtable.h:411:27: error: Expected ( after __context__ statement
.../rhashtable.h:411:27: error: got ;
I suspect it's best to remove the above.
...
next prev parent reply other threads:[~2025-06-13 14:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 15:40 [PATCH net-next v9 00/15] Begin upstreaming Homa transport protocol John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 01/15] net: homa: define user-visible API for Homa John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 02/15] net: homa: create homa_wire.h John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 03/15] net: homa: create shared Homa header files John Ousterhout
2025-06-13 14:40 ` Simon Horman [this message]
2025-06-13 18:36 ` John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 04/15] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 05/15] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2025-06-13 14:39 ` Simon Horman
2025-06-13 17:12 ` John Ousterhout
2025-06-13 17:18 ` Simon Horman
2025-06-13 18:02 ` John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 06/15] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2025-06-13 14:42 ` Simon Horman
2025-06-13 18:47 ` John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 07/15] net: homa: create homa_interest.h and homa_interest John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 08/15] net: homa: create homa_pacer.h and homa_pacer.c John Ousterhout
2025-06-13 14:43 ` Simon Horman
2025-06-13 18:50 ` John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 09/15] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 10/15] net: homa: create homa_outgoing.c John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 11/15] net: homa: create homa_utils.c John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 12/15] net: homa: create homa_incoming.c John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 13/15] net: homa: create homa_timer.c John Ousterhout
2025-06-13 14:41 ` Simon Horman
2025-06-13 18:44 ` John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 14/15] net: homa: create homa_plumbing.c John Ousterhout
2025-06-09 15:40 ` [PATCH net-next v9 15/15] net: homa: create Makefile and Kconfig John Ousterhout
-- strict thread matches above, loose matches on Subject: below --
2025-05-26 4:28 [PATCH net-next v9 00/15] Begin upstreaming Homa transport protocol John Ousterhout
2025-05-26 4:28 ` [PATCH net-next v9 03/15] net: homa: create shared Homa header files 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=20250613144055.GI414686@horms.kernel.org \
--to=horms@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@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.