From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, Geliang Tang <geliangtang@gmail.com>,
mptcp@lists.01.org, davem@davemloft.net,
Matthieu Baerts <matthieu.baerts@tessares.net>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 5/6] mptcp: add a new sysctl add_addr_timeout
Date: Mon, 2 Nov 2020 16:35:18 -0800 (PST) [thread overview]
Message-ID: <49dec7ac-934a-2fe6-70ef-71f7b3ed2f@linux.intel.com> (raw)
In-Reply-To: <20201102153359.29c546f1@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
On Mon, 2 Nov 2020, Jakub Kicinski wrote:
> On Fri, 30 Oct 2020 15:45:05 -0700 Mat Martineau wrote:
>> From: Geliang Tang <geliangtang@gmail.com>
>>
>> This patch added a new sysctl, named add_addr_timeout, to control the
>> timeout value (in seconds) of the ADD_ADDR retransmission.
>
> Please document the new sysctl.
>
Thanks Jakub. I will add a patch to document this new sysctl and the
existing 'enabled' sysctl for MPTCP.
--
Mat Martineau
Intel
next prev parent reply other threads:[~2020-11-03 0:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 22:45 [PATCH net-next 0/6] mptcp: Miscellaneous MPTCP fixes Mat Martineau
2020-10-30 22:45 ` [PATCH net-next 1/6] mptcp: adjust mptcp receive buffer limit if subflow has larger one Mat Martineau
2020-10-30 22:45 ` [PATCH net-next 2/6] mptcp: use _fast lock version in __mptcp_move_skbs Mat Martineau
2020-10-30 22:45 ` [PATCH net-next 3/6] tcp: propagate MPTCP skb extensions on xmit splits Mat Martineau
2020-10-30 22:45 ` [PATCH net-next 4/6] mptcp: split mptcp_clean_una function Mat Martineau
2020-10-30 22:45 ` [PATCH net-next 5/6] mptcp: add a new sysctl add_addr_timeout Mat Martineau
2020-11-02 23:33 ` Jakub Kicinski
2020-11-03 0:35 ` Mat Martineau [this message]
2020-10-30 22:45 ` [PATCH net-next 6/6] selftests: mptcp: add ADD_ADDR timeout test case Mat Martineau
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=49dec7ac-934a-2fe6-70ef-71f7b3ed2f@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=davem@davemloft.net \
--cc=geliangtang@gmail.com \
--cc=kuba@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).