* Ingo Molnar <[email protected]> wrote: > could you check the -41-23 -RT kernel at the usual place: > > http://redhat.com/~mingo/realtime-preempt/ > > i've added Trond's radix lookup code, plus the lockbreaker patch. > > (one thing that is not covered yet is nfs_scan_list() - that still scans > a list. Trond, is that fixable too?) 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. Ingo
Attachment:
nfs-1682us-latency.bz2
Description: BZip2 compressed data
- Follow-Ups:
- Re: NFS client latencies
- From: Ingo Molnar <[email protected]>
- Re: NFS client latencies
- 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]>
- NFS client latencies
- Prev by Date: [RFC/PATCH] network configs: disconnect network options from drivers
- Next by Date: Re: Latency tests with 2.6.12-rc1
- Previous by thread: Re: NFS client latencies
- Next by thread: Re: NFS client latencies
- Index(es):