On Mon, 30 May 2016 17:16:24 +1000, David Gwynne wrote: > llinfo_nd6 thinks its expiry may extend beyond a timeout interval. > > so it keeps track of the number of ticks it really wants via ln_ntick > in llinfo_nd6 and schedules multiple timeouts to reach it. > > i think this is a waste of time for two reasons: > > 1. nd6_llinfo_settimer() (which sets this up) doesnt seem to be > called with a timeout greater than what timeouts can handle. timeouts > off the wire are ignored if theyre greater than an hour > (MAX_REACHABLE_TIME), and the largest constant that ends up being > passed is a day via nd6_gctimer. the fastest ticking arch we have > is alpha with HZ at 1024, which wraps at about 24 days. we have > space. > > 2. ln_ntick is a long, which is the same size as int on 32 bit > archs. the semantics it wants dont exist on a bunch of platforms. > it is kind of arguing its own uselesness.
OK millert@ - todd
