[ECOS] Changing system timer resolution

[Grant Edwards]

On Mon, Dec 03, 2001 at 10:17:10AM -0700, Gary Thomas 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.
> > 
> > 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?

That's the only spot that I know of in the TCP stack itself.  I
thought there was someplace in the DHCP client code as well,
but I wasn't reading very carefully and may have missed
something.

-- 
Grant Edwards
grante@visi.com