Re: Drastic Slowdown of 'fseek()' Calls From 2.4 to 2.6 -- VMM Change?

[Robert Hancock <hancockr@shaw.ca>]

Marr wrote:
> Clearly, the 2.4.31 results are speedy because the whole 4MB file has been 
> cached.
I don't think this is clear at all. The entire file should always be 
cached, not doing this would be insane.
> What I cannot figure out is this: what has changed in 2.6.x kernels to cause 
> the performance to degrade so drastically?!?
fseek() is a C library call, not a system call itself - there may be 
something that glibc is doing differently. Are you using the same glibc 
version with both kernels?
Just from this program it could be something else entirely that explains 
the difference in speed, like the random number generator..
--
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

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