netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: John Ousterhout <ouster@cs.stanford.edu>, netdev@vger.kernel.org
Cc: edumazet@google.com, horms@kernel.org, kuba@kernel.org
Subject: Re: [PATCH net-next v8 01/15] net: homa: define user-visible API for Homa
Date: Mon, 5 May 2025 10:03:17 +0200	[thread overview]
Message-ID: <7addde54-1b77-4376-b976-655a2776a31e@redhat.com> (raw)
In-Reply-To: <20250502233729.64220-2-ouster@cs.stanford.edu>

On 5/3/25 1:37 AM, John Ousterhout wrote:
> +/* Flag bits for homa_sendmsg_args.flags (see man page for documentation):
> + */
> +#define HOMA_SENDMSG_PRIVATE       0x01
> +#define HOMA_SENDMSG_NONBLOCKING   0x02

It's unclear why you need to define a new mechanism instead of using
MSG_DONTWAIT. This is possibly not needed and deserves at least a good
motivation in the patch introducing it.

/P


  parent reply	other threads:[~2025-05-05  8:03 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 23:37 [PATCH net-next v8 00/15] Begin upstreaming Homa transport protocol John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 01/15] net: homa: define user-visible API for Homa John Ousterhout
2025-05-05  7:54   ` Paolo Abeni
2025-05-05 16:14     ` John Ousterhout
2025-05-05 16:48       ` Andrew Lunn
2025-05-05 17:52         ` John Ousterhout
2025-05-05  8:03   ` Paolo Abeni [this message]
2025-05-05 22:53     ` John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 02/15] net: homa: create homa_wire.h John Ousterhout
2025-05-05  8:28   ` Paolo Abeni
2025-05-05 23:54     ` John Ousterhout
2025-05-22  5:31     ` John Ousterhout
2025-05-22  7:36       ` Paolo Abeni
2025-05-02 23:37 ` [PATCH net-next v8 03/15] net: homa: create shared Homa header files John Ousterhout
2025-05-05 10:20   ` Paolo Abeni
2025-05-06 17:45     ` John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 04/15] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2025-05-05  9:51   ` Paolo Abeni
2025-05-06 23:28     ` John Ousterhout
2025-05-08  8:35       ` Paolo Abeni
2025-05-02 23:37 ` [PATCH net-next v8 05/15] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2025-05-05 11:06   ` Paolo Abeni
2025-05-07 16:11     ` John Ousterhout
2025-05-07 17:25       ` Andrew Lunn
2025-05-08  8:46       ` Paolo Abeni
2025-05-02 23:37 ` [PATCH net-next v8 06/15] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2025-05-05 16:46   ` Paolo Abeni
2025-05-07 18:30     ` John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 07/15] net: homa: create homa_interest.h and homa_interest John Ousterhout
2025-05-06 13:53   ` Paolo Abeni
2025-05-07 18:45     ` John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 08/15] net: homa: create homa_pacer.h and homa_pacer.c John Ousterhout
2025-05-06 14:05   ` Paolo Abeni
2025-05-07 18:55     ` John Ousterhout
2025-05-07 20:31       ` Andrew Lunn
2025-05-07 20:46         ` John Ousterhout
2025-05-22  7:49           ` Paolo Abeni
2025-05-02 23:37 ` [PATCH net-next v8 09/15] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 10/15] net: homa: create homa_outgoing.c John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 11/15] net: homa: create homa_utils.c John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 12/15] net: homa: create homa_incoming.c John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 13/15] net: homa: create homa_timer.c John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 14/15] net: homa: create homa_plumbing.c John Ousterhout
2025-05-02 23:37 ` [PATCH net-next v8 15/15] net: homa: create Makefile and Kconfig John Ousterhout
2025-05-06  5:04 ` [PATCH net-next v8 00/15] Begin upstreaming Homa transport protocol John Ousterhout
2025-05-06 12:01   ` Paolo Abeni

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=7addde54-1b77-4376-b976-655a2776a31e@redhat.com \
    --to=pabeni@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@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;
as well as URLs for NNTP newsgroup(s).