On 10/18/07, Mathieu Desnoyers <[email protected]> wrote:
> Good question indeed. How large is this memory footprint exactly ? If it
> is as small as you say, I suspect that the real issue could be that
> these variable are accessed by the scheduler critical paths and
> therefore trash the caches.
Maybe my wording was ambiguous, I meant to reduce cache line pollution
when accessing these schedstat fields.
As the original author, it was always my intention that schedstats be low
enough impact that it could be turned on all the time, if need be. That's
why, for the most part, it does increments and decrements of counters and
leaves the actual math to apps that might gather the data. Initial
measurements showed that it was having no measurable impact on performance.
Of course, that was years ago too. Systems (and hardware) have changed
considerably in that time. Are we talking theoretical cache pollution
or measured? And if measured, what effect is it having?
(sorry for the late followup; was on vacation ...)
Rick
-
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]
