From: Andrew Lunn <andrew@lunn.ch>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: Jiri Pirko <jiri@resnulli.us>,
Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org
Subject: Re: Upstream Homa?
Date: Sun, 13 Nov 2022 18:10:39 +0100 [thread overview]
Message-ID: <Y3ElDxZi6Hswga2D@lunn.ch> (raw)
In-Reply-To: <CAGXJAmzdr1dBZb4=TYscXtN66weRvsO6p74K-K3aa_7UJ=sEuQ@mail.gmail.com>
> Homa implements RPCs rather than streams like TCP or messages like
> UDP. An RPC consists of a request message sent from client to server,
> followed by a response message from server back to client. This requires
> additional information in the API beyond what is provided in the arguments to
> sendto and recvfrom. For example, when sending a request message, the
> kernel returns an RPC identifier back to the application; when waiting for
> a response, the application can specify that it wants to receive the reply for
> a specific RPC identifier (or, it can specify that it will accept any
> reply, or any
> request, or both).
This sounds like the ancillary data you can pass to sendmsg(). I've
not checked the code, it might be the current plumbing is only into to
the kernel, but i don't see why you cannot extend it to also allow
data to be passed back to user space. If this is new functionality,
maybe add a new flags argument to control it.
recvmsg() also has ancillary data.
Andrew
next prev parent reply other threads:[~2022-11-13 17:11 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
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 [this message]
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=Y3ElDxZi6Hswga2D@lunn.ch \
--to=andrew@lunn.ch \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=ouster@cs.stanford.edu \
--cc=stephen@networkplumber.org \
/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).