Andy Furniss wrote:
You are comparing two completely different ->systems<-. Please stop being
focused on HZ, ok ? HZ does not rule the priority of the in-kernel tasks.
OK - It was just that changing HZ sorted it on 2.4.
Hmm - I did some testing on old kernels, though I know I sorted it to
2ms I haven't got that kernel anymore and setting a vanilla 2.4.26 to hz
500 made the forwarded traffic cycle with 5ms not 2ms, local doesn't
cycle but isn't constant and gives 5ms varience.
I'll have to revisit that - thinking about it that could be because the
test pings from the box with the modem stayed in sync (and I got +0 to
+10ms steady depending on luck) and the timer on the LAN PC drifted and
caused the pattern like I posted.
I also still have two non vanilla - patched with a big patch which I
used for the QOS stuff but also contained preempt and a different Hz patch.
Being always low on disk space I have deleted the trees and can't see
the .configs - so don't know what Hz they use, I'll have to see now I've
thought of a way to test that.
The answer to the behavior of local traffic on these - 2.4.24 is always
+10ms, 2.4.21 is stable whatever the first ping is the rest will be, the
first ping time being between baseline +0ms to +10ms.
Forwarded cycles with the 10ms snap up/down - but this is only from
Linux, I tried pings from win98 and I get random +0 to 10ms.
Andy.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
