From: Cong Wang <xiyou.wangcong@gmail.com>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: netdev@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH net-next v2 00/12] Begin upstreaming Homa transport protocol
Date: Fri, 22 Nov 2024 13:42:49 -0800 [thread overview]
Message-ID: <Z0D62cS7DgkHYEDr@pop-os.localdomain> (raw)
In-Reply-To: <CAGXJAmwr5u7Don-nKivvTuj6C9pGT2A5cAXvhKo6sAm_hHy72A@mail.gmail.com>
On Tue, Nov 19, 2024 at 01:13:36PM -0800, John Ousterhout wrote:
> On Thu, Nov 14, 2024 at 8:59 AM John Ousterhout <ouster@cs.stanford.edu> wrote:
> >
> > On Wed, Nov 13, 2024 at 9:08 AM Cong Wang <xiyou.wangcong@gmail.com> wrote:
> >
> > > 2. Please consider adding socket diagnostics, see net/ipv4/inet_diag.c.
> >
> > I wasn't familiar with them before your email; I'll take a look.
>
> I have taken a look at socket diagnostics, and I agree that Homa
> should support them. However, this looks like a nontrivial task: there
> appears to be a fair amount of complexity there, not much
> documentation, and the current diagnostics appear pretty TCP-specific
> so it may take some work (and advice) to figure out how to map them
> onto Homa. Thus it feels like it will take a fair amount of
> back-and-forth to get this right. I would prefer to defer this until
> after the main body of Homa has been upstreamed, then have a patch
> series that is dedicated to socket diagnostics support, rather than
> lumping socket diagnostics into the current patch series. Is that OK
> with you?
>
Sure, I don't think it is a blocker here, it is just a nice feature to
promote Homa.
Thanks.
prev parent reply other threads:[~2024-11-22 21:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 23:39 [PATCH net-next v2 00/12] Begin upstreaming Homa transport protocol John Ousterhout
2024-11-11 23:39 ` [PATCH net-next v2 01/12] net: homa: define user-visible API for Homa John Ousterhout
2024-11-11 23:39 ` [PATCH net-next v2 02/12] net: homa: define Homa packet formats John Ousterhout
2024-11-11 23:39 ` [PATCH net-next v2 03/12] net: homa: create shared Homa header files John Ousterhout
2024-11-11 23:39 ` [PATCH net-next v2 04/12] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2024-11-11 23:39 ` [PATCH net-next v2 05/12] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2024-11-11 23:39 ` [PATCH net-next v2 06/12] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2024-11-11 23:40 ` [PATCH net-next v2 07/12] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2024-11-11 23:40 ` [PATCH net-next v2 08/12] net: homa: create homa_incoming.c John Ousterhout
2024-11-11 23:40 ` [PATCH net-next v2 09/12] net: homa: create homa_outgoing.c John Ousterhout
2024-11-11 23:40 ` [PATCH net-next v2 10/12] net: homa: create homa_timer.c John Ousterhout
2024-11-11 23:40 ` [PATCH net-next v2 11/12] net: homa: create homa_plumbing.c homa_utils.c John Ousterhout
2024-11-26 5:32 ` D. Wythe
2024-12-04 19:54 ` John Ousterhout
2024-12-02 3:51 ` D. Wythe
2024-12-03 1:51 ` Andrew Lunn
2024-12-09 6:45 ` D. Wythe
2024-12-05 19:49 ` John Ousterhout
2024-12-09 6:56 ` D. Wythe
2024-12-09 16:53 ` John Ousterhout
2024-12-09 17:03 ` John Ousterhout
2024-12-10 5:14 ` D. Wythe
2024-12-10 5:50 ` John Ousterhout
2024-12-10 6:13 ` D. Wythe
2024-11-11 23:40 ` [PATCH net-next v2 12/12] net: homa: create Makefile and Kconfig John Ousterhout
2024-11-11 23:52 ` Randy Dunlap
2024-11-12 0:11 ` John Ousterhout
2024-11-12 9:36 ` kernel test robot
2024-11-12 9:36 ` kernel test robot
2024-11-12 11:32 ` kernel test robot
2024-11-13 13:52 ` kernel test robot
2024-11-18 21:23 ` John Ousterhout
2024-11-26 4:13 ` D. Wythe
2024-11-26 4:27 ` D. Wythe
2024-12-02 23:27 ` John Ousterhout
2024-11-12 0:15 ` [PATCH net-next v2 00/12] Begin upstreaming Homa transport protocol Joe Damato
2024-11-12 6:06 ` John Ousterhout
2024-11-13 1:48 ` Jakub Kicinski
2024-11-13 18:18 ` John Ousterhout
2024-11-13 17:07 ` Cong Wang
2024-11-14 16:59 ` John Ousterhout
2024-11-14 19:36 ` Randy Dunlap
2024-11-19 21:13 ` John Ousterhout
2024-11-22 21:42 ` Cong Wang [this message]
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=Z0D62cS7DgkHYEDr@pop-os.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=linux-api@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox