I don't specifically remember discussions of TCP RTT estimates, but getting
better performance data everywhere, including network code, and reducing
latency in scheduler dependent wakeups of processes (better "interactive
feel"), as I remember the discussions. Some of the need for this is less
now that we have better performance tools and performance counters. I
was at least periperally involved early on in both MIPS and Alpha ports,
where the topic came up.
100hz == 10 ms == about 1/3 - 1/6 of human perception or your latency
budget for actions to be percieved as truly "instantaneous"; you
never can get latency back.
Given Jay's recent mail on the topic, I think things jibe with my memory:
the console is set that high in large part since we run that fast on other
operating systems; this got set as part of the initial experiments when
porting to new architectures; the cost of running at a high basic
rate is low enough that this was a rational design decision.
- Jim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/