[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20150114.002841.535982441503310505.davem@davemloft.net>
Date: Wed, 14 Jan 2015 00:28:41 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: jeff@...ix.org
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH] neighbour: fix base_reachable_time(_ms) not effective
immediatly when changed
From: Jean-Francois Remy <jeff@...ix.org>
Date: Wed, 14 Jan 2015 04:22:39 +0100
> When setting base_reachable_time or base_reachable_time_ms on a
> specific interface through sysctl or netlink, the reachable_time
> value is not updated.
>
> This means that neighbour entries will continue to be updated using the
> old value until it is recomputed in neigh_period_work (which
> recomputes the value every 300*HZ).
> On systems with HZ equal to 1000 for instance, it means 5mins before
> the change is effective.
>
> This patch changes this behavior by recomputing reachable_time after
> each set on base_reachable_time or base_reachable_time_ms.
> The new value will become effective the next time the neighbour's timer
> is triggered.
>
> Changes are made in two places: the netlink code for set and the sysctl
> handling code. For sysctl, I use a proc_handler. The ipv6 network
> code does provide its own handler but it already refreshes
> reachable_time correctly so it's not an issue.
> Any other user of neighbour which provide its own handlers must
> refresh reachable_time.
>
> Signed-off-by: Jean-Francois Remy <jeff@...ix.org>
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists