netdev - Advice on upstreaming Homa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAGXJAmxbJ7tN-8c0sT6WC_OBmJRTvrt-xvAZyQoM0HoNJFYycQ@mail.gmail.com>
Date: Thu, 26 Sep 2024 21:54:18 -0700
From: John Ousterhout <ouster@...stanford.edu>
To: netdev@...r.kernel.org
Subject: Advice on upstreaming Homa

I would like to start the process of upstreaming the Homa transport
protocol, and I'm writing for some advice.

Homa contains about 15 Klines of code. I have heard conflicting
suggestions about how much to break it up for the upstreaming process,
ranging from "just do it all in one patch set" to "it will need to be
chopped up into chunks of a few hundred lines". The all-at-once
approach is certainly easiest for me, and if it's broken up, the
upstreamed code won't be functional until a significant fraction of it
has been upstreamed. What's the recommended approach here?

I'm still pretty much a newbie when it comes to submitting Linux code.
Is there anyone with more experience who would be willing to act as my
guide? This would involve answering occasional questions and pointing
me to online information that I might otherwise miss, in order to
minimize the number of stupid things that I do.

I am happy to serve as maintainer for the code once it is uploaded. Is
it a prerequisite for there to be at least 2 maintainers?

Any other thoughts and suggestions are also welcome.

-John-