Re: [profile]: [0/23] mmap() support for /proc/profile

[Anton Blanchard]

Hi,

> Well, this is a little different. I was more concerned about the
> "Heisenberg effect" that the in-kernel copies to fetch profiling data
> had upon the data fetched. i.e. instead of idle time and the stuff I
> was looking for, I saw copy_to_user() and all kinds of vfs and /proc/
> crap instead, which blew what I was looking for completely out of the
> top 20. The profiling I did was on UP, which was done in part to
> eliminate lock contention as the cause of the phenomena I had observed.

Sure, I was just pointing out another area in our profiling code that 
warrants attention :)

Anton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/