* Ingo Molnar <[EMAIL PROTECTED]> wrote: > ok, find a new latency trace attached (1.6 msecs). I generated write > loads, and the nfs_scan_list_dirty() latency is gone and indeed > nfs_scan_list() generates the worst latency - while processing 8535 > pages in one critical section.
here's a more complete one of 4.4 msecs. (there was a bug in the latency
tracer that trimmed latency traces - this one is complete and shows an
nfs_scan_list processing of 22908 pages)
Ingo
nfs-4481us-latency.bz2
Description: BZip2 compressed data
