Nick Piggin <[email protected]> writes:
> This is with the filesystem mounted as noatime, so I can't work
> out why update_atime is so high on the list. I suspect maybe a
> false sharing issue with some other fields.
Did all the 64CPUs write to the same file?
Then update_atime was just the messenger - it is the first function
to read the inode so it eats the cache miss overhead.
Maybe adding a prefetch for it at the beginning of sys_read()
might help, but then with 64CPUs writing to parts of the inode
it will always thrash no matter how many prefetches.
-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]
