Lines Matching +full:many +full:- +full:to +full:- +full:one

5 :Authors: Greg Banks <gnb@sgi.com> - 26 Mar 2009
8 which the kernel NFS server makes available to userspace.  These
12 In most cases you don't need to know these formats, as the nfsstat(8)
13 program from the nfs-utils distribution provides a helpful command-line
30 a sequence of unsigned decimal numeric fields.  One line is shown
34 to zero these counters, instead applications should do their own
38 	The id number of the NFS thread pool to which this line applies.
48 packets-arrived
49 	Counts how many NFS packets have arrived.  More precisely, this
58 	However this is a more accurate and less workload-dependent measure
60 	due to NFS network traffic.
62 sockets-enqueued
63 	Counts how many times an NFS transport is enqueued to wait for
64 	an nfsd thread to service it, i.e. no nfsd thread was considered
68 	network-facing work to be done but it couldn't be done immediately,
70 	rate of change for this counter is zero; significantly non-zero
74 	pool for the NFS workload (the workload is thread-limited), in which
78 threads-woken
79 	Counts how many times an idle nfsd thread is woken to try to
83 	network-facing NFS work is being handled quickly, which is a good
85 	to but less than the rate of change of the packets-arrived counter.
87 threads-timedout
88 	Counts how many times an nfsd thread triggered an idle timeout,
89 	i.e. was not woken to handle any incoming network packets for
98 	 - Currently the rate at which the counter is incremented is quite
101 	   to be providing information that is still useful.
103 	 - It is usually a wise policy to provide some slack,
105 	   to allow for future spikes in load.
109 one of three ways.  An nfsd thread can be woken (threads-woken counts
111 (sockets-enqueued counts this case), or the packet can be temporarily
116 	packets-deferred = packets-arrived - ( sockets-enqueued + threads-woken )