Hi, Indeed, changing the timer to 1000Hz is possible, it turned out that I have a machine here running with a 1000Hz timer ticker. (I've installed a "realtime" kernel on it for audio recording). About your previous question, I've noticed that the system with 1000Hz ticker (which has been running for a few months) is UNSTABLE. might be more to it than just the 1000Hz, but I did notice that some "realtime" applications running in userspace where able to crash the system completely, happened 2 times in 3 months. Cheers, Jeroen. On Mon, 15 Mar 2004 11:37:16 +0000 Maria Joana Urbano <stmaria@xxxxxxxxx> wrote: > > >in pkt_sched.h: > > > >#define PSCHED_CLOCK_SOURCE PSCHED_CPU > > > >that's all, I wonder why it's not default to do this, or maybe it's an > >idea to make the packet scheduler detect the presence of tsc when the > >module is loaded. > > Hi, > > I think not all processors accept this #define PSCHED_CLOCK_SOURCE > PSCHED_CPU. At least, I couldn't do it in my router. > > I am not using HTB but TBF, but I think the timing problems are similar. As > to tune TBF with higher precision, I had to manually change Hz value from > 100 to 1000, in param.h, and actually I am getting better results. > > My question is, does anybody tried to do this in an production environment? > For instance, in a router that integrates traffic control, NAT, firewall, > services gateway, etc., can this change in HZ value harm in any way the > rest of the system? > > Thanks in advance, > Joana Urbano > _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
