[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAFXRd2xhSa_X2u-dCB_nM==_vLoV_GypNPzMugW=njBbnLr6g@mail.gmail.com>
Date: Wed, 28 May 2014 13:45:52 -0400
From: Milos Vyletel <milos.vyletel@...il.com>
To: David Miller <davem@...emloft.net>
Cc: cwang@...pensource.com, kuznet@....inr.ac.ru, jmorris@...ei.org,
yoshfuji@...ux-ipv6.org, kaber@...sh.net, netdev@...r.kernel.org,
"open list:X86 ARCHITECTURE..." <linux-kernel@...r.kernel.org>
Subject: Re: [patch net-next] net: ipv6: trigger action when setting conf.all sysctls
On Wed, May 21, 2014 at 4:31 PM, David Miller <davem@...emloft.net> wrote:
> From: Cong Wang <cwang@...pensource.com>
> Date: Wed, 21 May 2014 10:35:17 -0700
>
>> On Mon, May 19, 2014 at 10:09 AM, Milos Vyletel <milos.vyletel@...il.com> wrote:
>>> As it is right now most of these tunables don't do anything - they don't
>>> set any interface specific settings to the desired value and they don't
>>> take precedence before device specific settings in most cases.
>>>
>>> Documentation/networking/ip-sysctl.txt defines them to be:
>>> conf/all/*:
>>> Change all the interface-specific settings.
>>>
>>> but that is not really the case.
>>>
>>
>> I don't think it's a good idea, it enforces interface specific changes.
>>
>> You need to mimic what IPv4 conf does (if it hasn't done yet), something
>> like below:
>>
>> #define IN_DEV_MAXCONF(in_dev, attr) \
>> (max(IPV4_DEVCONF_ALL(dev_net(in_dev->dev), attr), \
>> IN_DEV_CONF_GET((in_dev), attr)))
>
> Agreed.
Thanks for the comments guys. I've looked at ipv4 sysctl code and I'm going to
align ipv6 code and add similar macros (IN6_DEV_{OR,MAX,AND}CONF).
Milos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists