* 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
Attachment:
nfs-4481us-latency.bz2
Description: BZip2 compressed data
- References:
- NFS client latencies
- From: Lee Revell <[email protected]>
- Re: NFS client latencies
- From: Trond Myklebust <[email protected]>
- Re: NFS client latencies
- From: Lee Revell <[email protected]>
- Re: NFS client latencies
- From: Trond Myklebust <[email protected]>
- Re: NFS client latencies
- From: Andrew Morton <[email protected]>
- Re: NFS client latencies
- From: Trond Myklebust <[email protected]>
- Re: NFS client latencies
- From: Lee Revell <[email protected]>
- Re: NFS client latencies
- From: Ingo Molnar <[email protected]>
- Re: NFS client latencies
- From: Ingo Molnar <[email protected]>
- NFS client latencies
- Prev by Date: Re: Latency tests with 2.6.12-rc1
- Next by Date: [PATCH] Kprobes: Allow/deny probes on int3/breakpoint instruction?
- Previous by thread: Re: NFS client latencies
- Next by thread: Continuing woes - Yenta PCMCIA and USB 2.0 Cardbus Card
- Index(es):
 |