From: Stephen Hemminger <stephen@networkplumber.org>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: netdev@vger.kernel.org
Subject: Re: Upstream Homa?
Date: Thu, 10 Nov 2022 13:25:40 -0800 [thread overview]
Message-ID: <20221110132540.44c9463c@hermes.local> (raw)
In-Reply-To: <CAGXJAmzTGiURc7+Xcr5A09jX3O=VzrnUQMp0K09kkh9GMaDy4A@mail.gmail.com>
On Thu, 10 Nov 2022 11:42:35 -0800
John Ousterhout <ouster@cs.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-
There are lots of experimental protocols already in Linux.
The usual upstream problem areas are:
- coding style
- compatibility layers
developers don't care about code to run on older versions or other OS.
- user API
once you define it hard to change, need to get it right
- tests
is there a way to make sure it works on all platforms
Heuristics and bug fixing are fine, in fact having a wider community
will help.
next prev parent reply other threads:[~2022-11-10 21:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 19:42 Upstream Homa? John Ousterhout
2022-11-10 21:25 ` Stephen Hemminger [this message]
2022-11-10 23:23 ` Andrew Lunn
[not found] ` <CAGXJAmw=NY17=6TnDh0oV9WTmNkQCe9Q9F3Z=uGjG9x5NKn7TQ@mail.gmail.com>
2022-11-11 19:10 ` Stephen Hemminger
2022-11-11 19:25 ` Andrew Lunn
2022-11-12 7:53 ` Jiri Pirko
2022-11-13 6:25 ` John Ousterhout
2022-11-13 17:10 ` Andrew Lunn
2022-11-13 20:10 ` John Ousterhout
2022-11-13 20:37 ` Andrew Lunn
2022-11-14 5:37 ` John Ousterhout
2022-11-13 6:09 ` John Ousterhout
2022-11-13 8:24 ` Jiri Pirko
2022-11-13 18:53 ` Andrew Lunn
2022-12-04 18:17 ` Jamal Hadi Salim
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=20221110132540.44c9463c@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=ouster@cs.stanford.edu \
/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.