netdev - Re: Upstream 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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAM0EoM=aekjeBdrvfuG4bV=VHEJ3X7=58DvF5ZT2U3nzBAbo0w@mail.gmail.com>
Date:   Sun, 4 Dec 2022 13:17:03 -0500
From:   Jamal Hadi Salim <jhs@...atatu.com>
To:     John Ousterhout <ouster@...stanford.edu>
Cc:     netdev@...r.kernel.org
Subject: Re: Upstream Homa?

And for folks interested in John's work, we just posted his excellent keynote
slides+video from netdevconf 0x16. See:
https://netdevconf.info/0x16/session.html?keynote-ousterhout

cheers,
jamal

On Thu, Nov 10, 2022 at 2:43 PM John Ousterhout <ouster@...stanford.edu> wrote:
>
> Several people at the netdev conference asked me if I was working to
> upstream the Homa transport protocol into the kernel. I have assumed
> that this is premature, given that there is not yet significant usage of
> Homa, but they encouraged me to start a discussion about upstreaming
> with the netdev community.
>
> So, I'm sending this message to ask for advice about (a) what state
> Homa needs to reach before it would be appropriate to upstream it,
> and, (b) if/when that time is reached, what is the right way to go about it.
> Homa currently has about 13K lines of code, which I assume is far too
> large for a single patch set; at the same time, it's hard to envision a
> manageable first patch set with enough functionality to be useful by itself.
>
> -John-