> hmm stolen time could even be useful without virtualization; to a large
> degree, if cpufreq reduces the speed of your cpu you have "stolen
> cycles" that way... I wonder if this concept can be used for that as
> well...
If you mean it for the real time clock: Doesn't make sense then
because Linux time isn't measured in cycles
If you mean it for the scheduler: it only uses estimates for
relative fairness. As long as everybody is sloeed down in the same
way the relative fairness doesn't change.
For time accounting: the regular timer interrupt is fairly imprecise
anyawys because it samples at a low frequency. While it would be possible to
improve this it would be quite costly by slowing down interrupts and syscalls.
I'm not sure it makes that much difference here either.
I don't see the point, frankly.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
