NFSD duplicate reply cache optimizations
Subsystems (2)
Chuck Lever
maintainerv2 cover NFSD duplicate reply cache optimizations
From: Chuck Lever <[email protected]>
Two minor optimizations for the NFSD duplicate reply cache. These showed slight improvement in WRITE throughput on exported fast file systems.
Changes since v1:
- Remove RC_INPROG check from nfsd_prune_bucket_locked()
Chuck Lever (2):
NFSD: Delay adding new entries to LRU
NFSD: Reduce DRC bucket size
fs/nfsd/nfscache.c | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-)
Signature · 1 line
2.50.0
Chuck Lever
maintainerPATCH v2 1/2 NFSD: Delay adding new entries to LRU
From: Chuck Lever <[email protected]>
Neil Brown observes:
Quoted 3 lines
I would not include
RC_INPROGentries in the lru at all - they are always ignored, and will be added when they are switched toRCU_DONE.
I also removed a stale comment.
--- fs/nfsd/nfscache.c | 13 ------------- 1 file changed, 13 deletions(-)
fs/nfsd/nfscache.c +0 -13
@@ -237,10 +237,6 @@ void nfsd_reply_cache_shutdown(struct nfsd_net *nn) } -/* -* Move cache entry to end of LRU list, and queue the cleaner to run if it's -* not already scheduled. -*/ static void lru_put_end (struct nfsd_drc_bucket *b,struct nfsd_cacherep *rp) {
@@ -272,13 +268,6 @@ nfsd_prune_bucket_locked(struct nfsd_net *nn, struct nfsd_drc_bucket *b,/* The bucket LRU is ordered oldest-first. */ list_for_each_entry_safe (rp, tmp, &b->lru_head, c_lru) { -/* -* Don't free entries attached to calls that are still -* in-progress, but do keep scanning the list. -*/ -if (rp->c_state ==RC_INPROG ) -continue ; -if (atomic_read (&nn->num_drc_entries) <= nn->max_drc_entries &&time_before (expiry, rp->c_timestamp))break ;
@@ -453,8 +442,6 @@ nfsd_cache_insert(struct nfsd_drc_bucket *b, struct nfsd_cacherep *key, nn->longest_chain_cachesize, atomic_read(&nn->num_drc_entries)); } - -lru_put_end (b, ret);return ret; }
Signature · 1 line
2.50.0
Chuck Lever
maintainerPATCH v2 2/2 NFSD: Reduce DRC bucket size
In reply to Chuck LeverFrom: Chuck Lever <[email protected]>
The common case is that a DRC lookup will not find the XID in the bucket. Reduce the amount of pointer chasing during the lookup by keeping fewer entries in each hash bucket.
Changing the bucket size constant forces the size of the DRC hash table to increase, and the height of each bucket r-b tree to be reduced.
--- fs/nfsd/nfscache.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/nfsd/nfscache.c +1 -1
@@ -27,7 +27,7 @@* cache size, the idea being that when the cache is at its maximum number * of entries, then this should be the average number of entries per bucket. */ -#define TARGET_BUCKET_SIZE 64 +#define TARGET_BUCKET_SIZE 8struct nfsd_drc_bucket {struct rb_root rb_head;
Signature · 1 line
2.50.0