]> git.karo-electronics.de Git - karo-tx-linux.git/commit
nvme: only consider exit latency when choosing useful non-op power states
authorKai-Heng Feng <kai.heng.feng@canonical.com>
Wed, 7 Jun 2017 07:25:42 +0000 (15:25 +0800)
committerChristoph Hellwig <hch@lst.de>
Wed, 7 Jun 2017 09:08:54 +0000 (11:08 +0200)
commitda87591bea92204fcb921bac927666eb7141908e
treef23d1207718ee18218ce4267cbcb0f361456e818
parent24b7f0592f738a1127c72dbf5b72a83997dd6997
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>
drivers/nvme/host/core.c