From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH mptcp-next] docs: networking: mptcp: Add MPTCP sysctl entries
Date: Tue, 03 Nov 2020 10:13:32 -0800 [thread overview]
Message-ID: <c98c8213-694e-bd18-c2a1-bab564697e2@linux.intel.com> (raw)
In-Reply-To: f1b44785-2654-4cca-2bd5-9c80f4db7b1d@tessares.net
[-- Attachment #1: Type: text/plain, Size: 2837 bytes --]
On Tue, 3 Nov 2020, Matthieu Baerts wrote:
> Hi Mat,
>
> On 03/11/2020 02:55, Mat Martineau wrote:
>> Describe the two MPTCP sysctls, what the values mean, and the default
>> settings.
>>
>> Signed-off-by: Mat Martineau <mathew.j.martineau(a)linux.intel.com>
>> ---
>>
>> Jakub requested sysctl documentation for the 'add_addr_timeout' setting,
>> and we didn't have our 'enabled' sysctl documented either.
>
> Thanks for looking after this!
>
>> If this looks good to everyone I can add it to v2 the miscellaneous
>> series on the netdev list.
>
> Good idea! I just have one remark below!
>
> (...)
>
>> diff --git a/Documentation/networking/mptcp-sysctl.rst
>> b/Documentation/networking/mptcp-sysctl.rst
>> new file mode 100644
>> index 000000000000..70c076eb361d
>> --- /dev/null
>> +++ b/Documentation/networking/mptcp-sysctl.rst
>> @@ -0,0 +1,24 @@
>> +.. SPDX-License-Identifier: GPL-2.0
>> +
>> +====================
>> +MPTCP Sysfs variables
>> +====================
>
> The "s" at the end is going to fall :-/
>
> More seriously, if I am not mistaken, it is important to have at least the
> same amount of characters for the mark representing the title in RST.
>
> There are some RST validators or maybe try this: http://rst.ninjs.org
Ok, will fix that up.
>
>> +/proc/sys/net/mptcp/* Variables:
>> +===============================
>
> Same here: one "=" is missing.
>
> Note that for me, it is strange to add a ":" at the end of a title. They
> don't do that in ip-sysctl.rst but they do that in mpls-sysctl.rst.
> Personally, I would not add it.
>
> Should we give a very short introduction about MPTCP here? I guess not in
> this "-sysctl" file. Later when we will have a documentation for userspace.
Yes, I did start from a copy of mpls-sysctl.rst and inherited its quirks.
Happy to remove the colon. We do need to add MPTCP documentation but for
now I think we can start with the sysctl section.
>
>> +enabled - INTEGER
>> + Control whether MPTCP sockets can be created.
>
> Should we mention this?
>
> This is a per-namespace sysctl.
>
> For me, that's a very useful thing to know but often missing in the doc.
>
>> + MPTCP sockets can be created if the value is nonzero.
>> +
>> + Default: 1
>> +
>> +add_addr_timeout - INTEGER (seconds)
>> + Set the timeout after which an ADD_ADDR control message will be
>> + resent to an MPTCP peer that has not acknowledged a previous
>> + ADD_ADDR message.
>
> Here too, it is per-ns. I guess it would be good to repeat that for each
> sysctl. But because all of them are per-ns, we can also add something in the
> introduction, just under "/proc/sys/net/mptcp/* Variables". Up to you!
>
Will add the per-ns information.
Thanks for the review!
--
Mat Martineau
Intel
next reply other threads:[~2020-11-03 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 18:13 Mat Martineau [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-03 9:22 [MPTCP] Re: [PATCH mptcp-next] docs: networking: mptcp: Add MPTCP sysctl entries Matthieu Baerts
2020-11-03 2:54 Geliang Tang
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=c98c8213-694e-bd18-c2a1-bab564697e2@linux.intel.com \
--to=mptcp@lists.linux.dev \
/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