Lines Matching refs:threads

43 	which contains all the nfsd threads and all the CPUs in the system,
71 	This can happen either because there are too few nfsd threads in the
75 	configuring more nfsd threads will probably improve the performance
77 	already choosing not to wake idle nfsd threads because there are too
78 	many nfsd threads which want to run but cannot, so configuring more
79 	nfsd threads will make no difference whatsoever.  The overloads-avoided
82 threads-woken
93 	nfsd thread, despite the presence of idle nfsd threads, because
94 	too many nfsd threads had been recently woken but could not get
99 	runnable nfsd threads.  The ideal rate of change for this counter
117 	If this pattern is seen, configuring more nfsd threads will *not*
121 threads-timedout
127 	threads configured than can be used by the NFS workload.  This is
128 	a clue that the number of nfsd threads can be reduced without
143 one of three ways.  An nfsd thread can be woken (threads-woken counts
150 packets-deferred = packets-arrived - ( sockets-enqueued + threads-woken )