From: David Miller <davem@davemloft.net>
To: edumazet@google.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com, weiwan@google.com
Subject: Re: [PATCH net-next 0/2] net: Namespace-ify sysctl_tcp_rmem and sysctl_tcp_wmem
Date: Fri, 10 Nov 2017 14:35:19 +0900 (KST) [thread overview]
Message-ID: <20171110.143519.969350100852914123.davem@davemloft.net> (raw)
In-Reply-To: <20171107082928.22950-1-edumazet@google.com>
From: Eric Dumazet <edumazet@google.com>
Date: Tue, 7 Nov 2017 00:29:26 -0800
> We need to get per netns sysctl for sysctl_[proto]_rmem and
> sysctl_[proto]_wmem
>
> This patch series adds the basic infrastructure allowing per proto
> conversion, and takes care of TCP.
Series applied, thanks Eric.
prev parent reply other threads:[~2017-11-10 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 8:29 [PATCH net-next 0/2] net: Namespace-ify sysctl_tcp_rmem and sysctl_tcp_wmem Eric Dumazet
2017-11-07 8:29 ` [PATCH net-next 1/2] net: allow per netns sysctl_rmem and sysctl_wmem for protos Eric Dumazet
2017-11-07 8:29 ` [PATCH net-next 2/2] tcp: Namespace-ify sysctl_tcp_rmem and sysctl_tcp_wmem Eric Dumazet
2017-11-10 5:35 ` David Miller [this message]
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=20171110.143519.969350100852914123.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=weiwan@google.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).