netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ani Sinha <ani@arista.com>
To: David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: route/max_size sysctl in ipv4
Date: Tue, 6 Jan 2015 17:56:26 -0800	[thread overview]
Message-ID: <CAOxq_8MoPocarmhdXQOkc=4HfGh1L+5-ozEdwPzn2K8q4Gh55w@mail.gmail.com> (raw)
In-Reply-To: <20150105.195128.794605376092864881.davem@davemloft.net>

On Mon, Jan 5, 2015 at 4:51 PM, David Miller <davem@davemloft.net> wrote:

> The sysctl is kept so that scripts reading it don't suddenly stop
> working.  We can't just remove sysctl values.

Interestingly, one of our scripts did break. It broke because now this
sysctl is only available in the global net namespace and not in the
child namespaces. If not breaking scripts is the fundamental logic in
keeping in sysctl intact, would you guys be open to accepting a patch
where we make this sysctl available for all net namespaces?

  parent reply	other threads:[~2015-01-07  1:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 23:48 route/max_size sysctl in ipv4 Ani Sinha
2015-01-06  0:36 ` David Miller
2015-01-06  0:43   ` Ani Sinha
2015-01-06  0:51     ` David Miller
2015-01-06  0:56       ` Ani Sinha
2015-01-06 12:41         ` Pádraig Brady
2015-01-06 17:11           ` Ani Sinha
2015-01-06 18:09             ` Eric Dumazet
2015-01-06 20:05               ` Ani Sinha
2015-01-07  1:56       ` Ani Sinha [this message]
2015-01-08  1:25         ` Ani Sinha
2015-01-08  2:19           ` Eric Dumazet
2015-01-08  3:40             ` Ani Sinha
2015-01-08  5:41               ` Eric Dumazet
2015-01-08 18:39                 ` Ani Sinha
2015-01-08 19:03                   ` Eric Dumazet
2015-01-08 20:13                     ` Ani Sinha
2015-01-08 20:18                       ` Eric Dumazet
2015-01-09 18:47                       ` Cong Wang
2015-01-09 19:08                         ` Ani Sinha
2015-01-09 19:37                           ` Cong Wang
2015-01-09 21:23                             ` Ani Sinha

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='CAOxq_8MoPocarmhdXQOkc=4HfGh1L+5-ozEdwPzn2K8q4Gh55w@mail.gmail.com' \
    --to=ani@arista.com \
    --cc=davem@davemloft.net \
    --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).