[ECOS] Changing system timer resolution

[Gary Thomas]

On Mon, 2001-12-03 at 09:34, Jonathan Larmour wrote:
> Grant Edwards wrote:
> > 
> > On Mon, Dec 03, 2001 at 11:40:36AM +0000, Nick Garnett wrote:
> > 
> > > They should work now. Any TCP/DHCP code that relies on times should be
> > > using the timing facilities provided in the network or POSIX APIs( e.g.
> > > select() nanosleep() etc.).
> > 
> > Excellent! My source tree is getting old and I hadn't realized this had been
> > done.  Last time I looked at TCP stuff I think there was a hard-wired
> > definition of HZ, and I thought that changing the tick period would break
> > things.  At one point (a long time ago) I did have my system tick at 1ms for
> > a while, but I wasn't doing any network stuff at the time.
> 
> I think the idea is that the stack can be presented with something that
> looks like HZ == 100, but it actually isn't.
> 
> But looking closer, I'm not sure this has been fixed:
> net/tcpip/current/src/ecos/timeout.c doesn't scale the number of ticks at
> all.

Actually, I would think the only thing that would need attention is:
  net/tcpip/current/src/ecos/support.c: int hz = 100;
to make it work when the tick frequency is not 100Hz.

Was there some specific function/detail you were referring to?