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
128 lines
3.5 KiB
Text
128 lines
3.5 KiB
Text
perf-timechart(1)
|
|
=================
|
|
|
|
NAME
|
|
----
|
|
perf-timechart - Tool to visualize total system behavior during a workload
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'perf timechart' [<timechart options>] {record} [<record options>]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
There are two variants of perf timechart:
|
|
|
|
'perf timechart record <command>' to record the system level events
|
|
of an arbitrary workload. By default timechart records only scheduler
|
|
and CPU events (task switches, running times, CPU power states, etc),
|
|
but it's possible to record IO (disk, network) activity using -I argument.
|
|
|
|
'perf timechart' to turn a trace into a Scalable Vector Graphics file,
|
|
that can be viewed with popular SVG viewers such as 'Inkscape'. Depending
|
|
on the events in the perf.data file, timechart will contain scheduler/cpu
|
|
events or IO events.
|
|
|
|
In IO mode, every bar has two charts: upper and lower.
|
|
Upper bar shows incoming events (disk reads, ingress network packets).
|
|
Lower bar shows outgoing events (disk writes, egress network packets).
|
|
There are also poll bars which show how much time application spent
|
|
in poll/epoll/select syscalls.
|
|
|
|
TIMECHART OPTIONS
|
|
-----------------
|
|
-o::
|
|
--output=::
|
|
Select the output file (default: output.svg)
|
|
-i::
|
|
--input=::
|
|
Select the input file (default: perf.data unless stdin is a fifo)
|
|
-w::
|
|
--width=::
|
|
Select the width of the SVG file (default: 1000)
|
|
-P::
|
|
--power-only::
|
|
Only output the CPU power section of the diagram
|
|
-T::
|
|
--tasks-only::
|
|
Don't output processor state transitions
|
|
-p::
|
|
--process::
|
|
Select the processes to display, by name or PID
|
|
-f::
|
|
--force::
|
|
Don't complain, do it.
|
|
--symfs=<directory>::
|
|
Look for files with symbols relative to this directory.
|
|
-n::
|
|
--proc-num::
|
|
Print task info for at least given number of tasks.
|
|
-t::
|
|
--topology::
|
|
Sort CPUs according to topology.
|
|
--highlight=<duration_nsecs|task_name>::
|
|
Highlight tasks (using different color) that run more than given
|
|
duration or tasks with given name. If number is given it's interpreted
|
|
as number of nanoseconds. If non-numeric string is given it's
|
|
interpreted as task name.
|
|
--io-skip-eagain::
|
|
Don't draw EAGAIN IO events.
|
|
--io-min-time=<nsecs>::
|
|
Draw small events as if they lasted min-time. Useful when you need
|
|
to see very small and fast IO. It's possible to specify ms or us
|
|
suffix to specify time in milliseconds or microseconds.
|
|
Default value is 1ms.
|
|
--io-merge-dist=<nsecs>::
|
|
Merge events that are merge-dist nanoseconds apart.
|
|
Reduces number of figures on the SVG and makes it more render-friendly.
|
|
It's possible to specify ms or us suffix to specify time in
|
|
milliseconds or microseconds.
|
|
Default value is 1us.
|
|
|
|
RECORD OPTIONS
|
|
--------------
|
|
-P::
|
|
--power-only::
|
|
Record only power-related events
|
|
-T::
|
|
--tasks-only::
|
|
Record only tasks-related events
|
|
-I::
|
|
--io-only::
|
|
Record only io-related events
|
|
-g::
|
|
--callchain::
|
|
Do call-graph (stack chain/backtrace) recording
|
|
|
|
EXAMPLES
|
|
--------
|
|
|
|
$ perf timechart record git pull
|
|
|
|
[ perf record: Woken up 13 times to write data ]
|
|
[ perf record: Captured and wrote 4.253 MB perf.data (~185801 samples) ]
|
|
|
|
$ perf timechart
|
|
|
|
Written 10.2 seconds of trace to output.svg.
|
|
|
|
Record system-wide timechart:
|
|
|
|
$ perf timechart record
|
|
|
|
then generate timechart and highlight 'gcc' tasks:
|
|
|
|
$ perf timechart --highlight gcc
|
|
|
|
Record system-wide IO events:
|
|
|
|
$ perf timechart record -I
|
|
|
|
then generate timechart:
|
|
|
|
$ perf timechart
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkperf:perf-record[1]
|