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 05/15] net: homa: create homa_peer.h and homa_peer.c
Date: Fri, 13 Jun 2025 18:18:33 +0100 [thread overview]
Message-ID: <20250613171833.GN414686@horms.kernel.org> (raw)
In-Reply-To: <CAGXJAmxQn_iAqhOHwxEQ16n+MKjFyEbiUoBbGyDY+TLYooeJhQ@mail.gmail.com>
On Fri, Jun 13, 2025 at 10:12:11AM -0700, John Ousterhout wrote:
> (I have implemented all of your suggestions for which there are no
> responses below)
>
> On Fri, Jun 13, 2025 at 7:40 AM Simon Horman <horms@kernel.org> wrote:
> > > +/**
> > > + * homa_peer_hash() - Hash function used for @peertab->ht.
> > > + * @data: Pointer to key for which a hash is desired. Must actually
> > > + * be a struct homa_peer_key.
> > > + * @dummy: Not used
> > > + * @seed: Seed for the hash.
> > > + * Return: A 32-bit hash value for the given key.
> > > + */
> > > +static inline u32 homa_peer_hash(const void *data, u32 dummy, u32 seed)
> >
> > Sorry if this has already been asked but can homa reuse the code in
> > drivers/md/dm-vdo/murmurhash3.c:murmurhash3_128() (after moving it
> > somewhere else).
>
> No problem; the question hasn't been asked before. I'd be happy to use
> an existing implementation of murmurhash3 but couldn't find one that
> was accessible. What do you mean by "moving it somewhere else"? Are
> you suggesting I add a new murmurhash3 implementation somewhere
> "public" in the kernel? I'm a little hesitant to do this because I'm
> not at all expert on murmurhash3: I'm not confident about getting this
> right. Also, I wouldn't feel comfortable taking on maintainer
> responsibility for this.
Hi John,
I'm suggesting moving murmurhash3_128(), say to lib/ at the top
of the Kernel tree. And I'm happy to assist with this.
Aside from being accessible, does murmurhash3_128() meet your
needs in it's current form?
>
> > > + const struct homa_peer *peer = obj;
> > > + const struct homa_peer_key *key = arg->key;
> >
> > nit: Reverse xmas tree here please.
> > Likewise elsewhere in this patchset.
> >
> > This tool can he useful here
> > https://github.com/ecree-solarflare/xmastree/commits/master/
>
> Thanks for the pointer to xmastree.pl; I wasn't aware of it and it
> will be super-helpful. I've fixed all of the reverse xmas tree issues
> now.
>
> -John-
>
next prev parent reply other threads:[~2025-06-13 17:18 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
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 [this message]
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 05/15] net: homa: create homa_peer.h and homa_peer.c 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=20250613171833.GN414686@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.