16c00db4bb
Pull AFS fixes from David Howells:
"Here's a set of patches that fix a number of bugs in the in-kernel AFS
client, including:
- Fix directory locking to not use individual page locks for
directory reading/scanning but rather to use a semaphore on the
afs_vnode struct as the directory contents must be read in a single
blob and data from different reads must not be mixed as the entire
contents may be shuffled about between reads.
- Fix address list parsing to handle port specifiers correctly.
- Only give up callback records on a server if we actually talked to
that server (we might not be able to access a server).
- Fix some callback handling bugs, including refcounting,
whole-volume callbacks and when callbacks actually get broken in
response to a CB.CallBack op.
- Fix some server/address rotation bugs, including giving up if we
can't probe a server; giving up if a server says it doesn't have a
volume, but there are more servers to try.
- Fix the decoding of fetched statuses to be OpenAFS compatible.
- Fix the handling of server lookups in Cache Manager ops (such as
CB.InitCallBackState3) to use a UUID if possible and to handle no
server being found.
- Fix a bug in server lookup where not all addresses are compared.
- Fix the non-encryption of calls that prevents some servers from
being accessed (this also requires an AF_RXRPC patch that has
already gone in through the net tree).
There's also a patch that adds tracepoints to log Cache Manager ops
that don't find a matching server, either by UUID or by address"
* tag 'afs-fixes-20180514' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs:
afs: Fix the non-encryption of calls
afs: Fix CB.CallBack handling
afs: Fix whole-volume callback handling
afs: Fix afs_find_server search loop
afs: Fix the handling of an unfound server in CM operations
afs: Add a tracepoint to record callbacks from unlisted servers
afs: Fix the handling of CB.InitCallBackState3 to find the server by UUID
afs: Fix VNOVOL handling in address rotation
afs: Fix AFSFetchStatus decoder to provide OpenAFS compatibility
afs: Fix server rotation's handling of fileserver probe failure
afs: Fix refcounting in callback registration
afs: Fix giving up callbacks on server destruction
afs: Fix address list parsing
afs: Fix directory page locking
77 lines
1.8 KiB
Text
77 lines
1.8 KiB
Text
perf-kmem(1)
|
|
============
|
|
|
|
NAME
|
|
----
|
|
perf-kmem - Tool to trace/measure kernel memory properties
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'perf kmem' {record|stat} [<options>]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
There are two variants of perf kmem:
|
|
|
|
'perf kmem record <command>' to record the kmem events
|
|
of an arbitrary workload.
|
|
|
|
'perf kmem stat' to report kernel memory statistics.
|
|
|
|
OPTIONS
|
|
-------
|
|
-i <file>::
|
|
--input=<file>::
|
|
Select the input file (default: perf.data unless stdin is a fifo)
|
|
|
|
-f::
|
|
--force::
|
|
Don't do ownership validation
|
|
|
|
-v::
|
|
--verbose::
|
|
Be more verbose. (show symbol address, etc)
|
|
|
|
--caller::
|
|
Show per-callsite statistics
|
|
|
|
--alloc::
|
|
Show per-allocation statistics
|
|
|
|
-s <key[,key2...]>::
|
|
--sort=<key[,key2...]>::
|
|
Sort the output (default: 'frag,hit,bytes' for slab and 'bytes,hit'
|
|
for page). Available sort keys are 'ptr, callsite, bytes, hit,
|
|
pingpong, frag' for slab and 'page, callsite, bytes, hit, order,
|
|
migtype, gfp' for page. This option should be preceded by one of the
|
|
mode selection options - i.e. --slab, --page, --alloc and/or --caller.
|
|
|
|
-l <num>::
|
|
--line=<num>::
|
|
Print n lines only
|
|
|
|
--raw-ip::
|
|
Print raw ip instead of symbol
|
|
|
|
--slab::
|
|
Analyze SLAB allocator events.
|
|
|
|
--page::
|
|
Analyze page allocator events
|
|
|
|
--live::
|
|
Show live page stat. The perf kmem shows total allocation stat by
|
|
default, but this option shows live (currently allocated) pages
|
|
instead. (This option works with --page option only)
|
|
|
|
--time=<start>,<stop>::
|
|
Only analyze samples within given time window: <start>,<stop>. Times
|
|
have the format seconds.microseconds. If start is not given (i.e., time
|
|
string is ',x.y') then analysis starts at the beginning of the file. If
|
|
stop time is not given (i.e, time string is 'x.y,') then analysis goes
|
|
to end of file.
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkperf:perf-record[1]
|