diff options
author | 2017-06-07 15:25:42 +0800 | |
---|---|---|
committer | 2017-06-07 11:08:54 +0200 | |
commit | da87591bea92204fcb921bac927666eb7141908e (patch) | |
tree | f23d1207718ee18218ce4267cbcb0f361456e818 /tools/perf/scripts/python/call-graph-from-sql.py | |
parent | nvme-fc: fix missing put reference on controller create failure (diff) | |
download | linux-dev-da87591bea92204fcb921bac927666eb7141908e.tar.xz linux-dev-da87591bea92204fcb921bac927666eb7141908e.zip |
nvme: only consider exit latency when choosing useful non-op power states
When a NVMe is in non-op states, the latency is exlat.
The latency will be enlat + exlat only when the NVMe tries to transit
from operational state right atfer it begins to transit to
non-operational state, which should be a rare case.
Therefore, as Andy Lutomirski suggests, use exlat only when deciding power
states to trainsit to.
Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions