From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: [PATCH v2 net-next 00/15] tcp: move 14 sysctls to namespaces
Date: Thu, 26 Oct 2017 21:54:55 -0700 [thread overview]
Message-ID: <20171027045510.5827-1-edumazet@google.com> (raw)
Ideally all TCP sysctls should be per netns.
This patch series takes care of 14 of sysctls.
More to come later.
Eric Dumazet (15):
tcp: Namespace-ify sysctl_tcp_early_retrans
tcp: Namespace-ify sysctl_tcp_recovery
tcp: Namespace-ify sysctl_tcp_thin_linear_timeouts
tcp: Namespace-ify sysctl_tcp_slow_start_after_idle
tcp: Namespace-ify sysctl_tcp_retrans_collapse
tcp: Namespace-ify sysctl_tcp_stdurg
tcp: Namespace-ify sysctl_tcp_rfc1337
tcp: Namespace-ify sysctl_tcp_abort_on_overflow
tcp: Namespace-ify sysctl_tcp_fack
tcp: remove stale sysctl_tcp_reordering
tcp: Namespace-ify sysctl_tcp_max_reordering
tcp: Namespace-ify sysctl_tcp_dsack
tcp: Namespace-ify sysctl_tcp_app_win
tcp: Namespace-ify sysctl_tcp_adv_win_scale
tcp: Namespace-ify sysctl_tcp_frto
include/net/netns/ipv4.h | 14 ++++
include/net/tcp.h | 27 ++----
net/ipv4/sysctl_net_ipv4.c | 204 ++++++++++++++++++++++-----------------------
net/ipv4/tcp.c | 2 +-
net/ipv4/tcp_input.c | 42 ++++------
net/ipv4/tcp_ipv4.c | 9 ++
net/ipv4/tcp_minisocks.c | 8 +-
net/ipv4/tcp_output.c | 14 ++--
net/ipv4/tcp_recovery.c | 2 -
net/ipv4/tcp_timer.c | 4 +-
10 files changed, 157 insertions(+), 169 deletions(-)
--
2.15.0.rc2.357.g7e34df9404-goog
next reply other threads:[~2017-10-27 4:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 4:54 Eric Dumazet [this message]
2017-10-27 4:54 ` [PATCH v2 net-next 01/15] tcp: Namespace-ify sysctl_tcp_early_retrans Eric Dumazet
2017-10-27 4:54 ` [PATCH v2 net-next 02/15] tcp: Namespace-ify sysctl_tcp_recovery Eric Dumazet
2017-10-27 4:54 ` [PATCH v2 net-next 03/15] tcp: Namespace-ify sysctl_tcp_thin_linear_timeouts Eric Dumazet
2017-10-27 4:54 ` [PATCH v2 net-next 04/15] tcp: Namespace-ify sysctl_tcp_slow_start_after_idle Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 05/15] tcp: Namespace-ify sysctl_tcp_retrans_collapse Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 06/15] tcp: Namespace-ify sysctl_tcp_stdurg Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 07/15] tcp: Namespace-ify sysctl_tcp_rfc1337 Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 08/15] tcp: Namespace-ify sysctl_tcp_abort_on_overflow Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 09/15] tcp: Namespace-ify sysctl_tcp_fack Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 10/15] tcp: remove stale sysctl_tcp_reordering Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 11/15] tcp: Namespace-ify sysctl_tcp_max_reordering Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 12/15] tcp: Namespace-ify sysctl_tcp_dsack Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 13/15] tcp: Namespace-ify sysctl_tcp_app_win Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 14/15] tcp: Namespace-ify sysctl_tcp_adv_win_scale Eric Dumazet
2017-10-27 4:55 ` [PATCH v2 net-next 15/15] tcp: Namespace-ify sysctl_tcp_frto Eric Dumazet
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=20171027045510.5827-1-edumazet@google.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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).