* Trond Myklebust <[email protected]> wrote: > > + int res; > ^^^^^^^ Should be "int res = 0;" your patch works fine here - but there are still latencies in nfs_scan_commit()/nfs_scan_list(): see the attached 3.7 msec latency trace. It happened during a simple big-file writeout and is easily reproducible. Could the nfsi->commit list searching be replaced with a radix based approach too? Ingo
Attachment:
nfs-3769us-latency.bz2
Description: BZip2 compressed data
- Follow-Ups:
- Re: NFS client latencies
- From: Trond Myklebust <[email protected]>
- Re: NFS client latencies
- References:
- Re: NFS client latencies
- From: Trond Myklebust <[email protected]>
- Re: NFS client latencies
- From: Lee Revell <[email protected]>
- Re: NFS client latencies
- From: Andrew Morton <[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: Ingo Molnar <[email protected]>
- Re: NFS client latencies
- From: Andrew Morton <[email protected]>
- Re: NFS client latencies
- From: Ingo Molnar <[email protected]>
- Re: NFS client latencies
- From: Trond Myklebust <[email protected]>
- Re: NFS client latencies
- From: Trond Myklebust <[email protected]>
- Re: NFS client latencies
- Prev by Date: Re: [PATCH] API for TRNG (2.6.11) [Fortuna]
- Next by Date: Re: Poor SATA / RAID performance (2.6.11 and promise SATAII150 TX4)
- Previous by thread: Re: NFS client latencies
- Next by thread: Re: NFS client latencies
- Index(es):
 |