From: "D. Wythe" <alibuda@linux.alibaba.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: John Ousterhout <ouster@cs.stanford.edu>,
netdev@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH net-next v2 11/12] net: homa: create homa_plumbing.c homa_utils.c
Date: Mon, 9 Dec 2024 14:45:52 +0800 [thread overview]
Message-ID: <a0358f1e-a63c-4059-adc8-d2f338710e36@linux.alibaba.com> (raw)
In-Reply-To: <fd5cf76f-48c3-4d73-9609-c13ccb622382@lunn.ch>
On 12/3/24 9:51 AM, Andrew Lunn wrote:
> On Mon, Dec 02, 2024 at 11:51:48AM +0800, D. Wythe wrote:
>>> +/**
>>> + * homa_setsockopt() - Implements the getsockopt system call for Homa sockets.
>>> + * @sk: Socket on which the system call was invoked.
>>> + * @level: Level at which the operation should be handled; will always
>>> + * be IPPROTO_HOMA.
>>> + * @optname: Identifies a particular setsockopt operation.
>>> + * @optval: Address in user space of information about the option.
>>> + * @optlen: Number of bytes of data at @optval.
>>> + * Return: 0 on success, otherwise a negative errno.
>>> + */
>>> +int homa_setsockopt(struct sock *sk, int level, int optname, sockptr_t optval,
>>> + unsigned int optlen)
>>> +{
>>> + struct homa_sock *hsk = homa_sk(sk);
>>> + struct homa_set_buf_args args;
>>> + int ret;
>>> +
>>> + if (level != IPPROTO_HOMA || optname != SO_HOMA_SET_BUF ||
>>> + optlen != sizeof(struct homa_set_buf_args))
>>> + return -EINVAL;
>>
>> SO_HOMA_SET_BUF is a bit odd here, maybe HOMA_RCVBUF ? which also can be
>> implemented in getsockopt.
>
> Please trim the text when replying to just the needed context. With
> pages and pages of useless quoted text it is easy to overlook your
> comments.
>
> Andrew
Got it. Thanks for advice.
D. Wythe
next prev parent reply other threads:[~2024-12-09 6:45 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 [this message]
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
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=a0358f1e-a63c-4059-adc8-d2f338710e36@linux.alibaba.com \
--to=alibuda@linux.alibaba.com \
--cc=andrew@lunn.ch \
--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;
as well as URLs for NNTP newsgroup(s).