wireguard-linux/fs/nfsd/trace.h, branch jd/unified-crypt-queue

nfsd: Add tracepoints for update of the expkey and export cache entries

2020-03-16T16:04:33Z

Signed-off-by: Trond Myklebust Signed-off-by: Chuck Lever

nfsd: Add tracepoints for exp_find_key() and exp_get_by_name()

2020-03-16T16:04:33Z

Add tracepoints for upcalls. Signed-off-by: Trond Myklebust Signed-off-by: Chuck Lever

nfsd: Add tracing to nfsd_set_fh_dentry()

2020-03-16T16:04:33Z

Add tracing to allow us to figure out where any stale filehandle issues may be originating from. Signed-off-by: Trond Myklebust Signed-off-by: Chuck Lever

nfsd: convert file cache to use over/underflow safe refcount

2020-02-06T16:22:55Z

Use the 'refcount_t' type instead of 'atomic_t' for improved refcounting safety. Signed-off-by: Trond Myklebust Signed-off-by: J. Bruce Fields

nfsd: Define the file access mode enum for tracing

2020-02-06T16:22:55Z

Signed-off-by: Trond Myklebust Signed-off-by: J. Bruce Fields

nfsd: Fix a perf warning

2020-02-06T16:22:54Z

perf does not know how to deal with a __builtin_bswap32() call, and complains. All other functions just store the xid etc in host endian form, so let's do that in the tracepoint for nfsd_file_acquire too. Signed-off-by: Trond Myklebust Signed-off-by: J. Bruce Fields

nfsd: add a new struct file caching facility to nfsd

2019-08-19T15:00:39Z

Currently, NFSv2/3 reads and writes have to open a file, do the read or write and then close it again for each RPC. This is highly inefficient, especially when the underlying filesystem has a relatively slow open routine. This patch adds a new open file cache to knfsd. Rather than doing an open for each RPC, the read/write handlers can call into this cache to see if there is one already there for the correct filehandle and NFS_MAY_READ/WRITE flags. If there isn't an entry, then we create a new one and attempt to perform the open. If there is, then we wait until the entry is fully instantiated and return it if it is at the end of the wait. If it's not, then we attempt to take over construction. Since the main goal is to speed up NFSv2/3 I/O, we don't want to close these files on last put of these objects. We need to keep them around for a little while since we never know when the next READ/WRITE will come in. Cache entries have a hardcoded 1s timeout, and we have a recurring workqueue job that walks the cache and purges any entries that have expired. Signed-off-by: Jeff Layton Signed-off-by: Weston Andros Adamson Signed-off-by: Richard Sharpe Signed-off-by: Trond Myklebust Signed-off-by: Trond Myklebust Signed-off-by: J. Bruce Fields

nfsd: Trace NFSv4 COMPOUND execution

2018-04-03T19:08:15Z

This helps record the identity and timing of the ops in each NFSv4 COMPOUND, replacing dprintk calls that did much the same thing. Signed-off-by: Chuck Lever Signed-off-by: J. Bruce Fields

nfsd: Add I/O trace points in the NFSv4 read proc

2018-04-03T19:08:15Z

NFSv4 read compound processing invokes nfsd_splice_read and nfs_readv directly, so the trace points currently in nfsd_read are not invoked for NFSv4 reads. Move the NFSD READ trace points to common helpers so that NFSv4 reads are captured. Also, record any local I/O error that occurs, the total count of bytes that were actually returned, and whether splice or vectored read was used. Signed-off-by: Chuck Lever Signed-off-by: J. Bruce Fields

nfsd: Add I/O trace points in the NFSv4 write path

2018-04-03T19:08:15Z

NFSv4 write compound processing invokes nfsd_vfs_write directly. The trace points currently in nfsd_write are not effective for NFSv4 writes. Move the trace points into the shared nfsd_vfs_write() helper. After the I/O, we also want to record any local I/O error that might have occurred, and the total count of bytes that were actually moved (rather than the requested number). Signed-off-by: Chuck Lever Signed-off-by: J. Bruce Fields