Thread (1 message) 1 message, 1 author, 2012-07-19

Re: [PATCH net/for-next V1 1/1] IB/ipoib: break linkage to neighbouring system

From: David Miller <hidden>
Date: 2012-07-19 17:08:50
Also in: linux-rdma

From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Date: Thu, 19 Jul 2012 19:20:41 +0300
On 7/19/2012 6:24 PM, Christoph Lameter wrote:
quoted
On Thu, 19 Jul 2012, Shlomo Pongartz wrote:
quoted
The garbage collection and stale times follow the default ipv4/6
neigh.default.gc_yyy
sysctl values, for example

net.ipv4.neigh.default.gc_interval = 30
net.ipv4.neigh.default.gc_stale_time = 60

If given access to these values from IPoIB, we will be happy
to integrate them into that logic
It looks like the values are hardcoded right now.
Two points here,

1s, they are indeed hard-coded since there's no define/enum
that holds their default values (or maybe we should add one now?), see
this code snippest from net/ipv4/arp.c
These numbers come from the IPV6 Neighbour Discovery RFCs.  IPV4
replicates the Neighbour Unreachability Detection schemes of IPV6 in
pretty much it's entirety, and therefore takes on the same timeout et
al. parameters.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help