diff options
| author | Andy Lutomirski <luto@kernel.org> | 2017-04-22 02:19:22 +0300 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2017-04-25 07:03:46 +0300 |
| commit | 76e4ad09a30cfb589eb436ad067f4abecb82cc04 (patch) | |
| tree | 75b30ca7e081fc3907d7b0ea2e632f438e138bd1 /drivers/nvme | |
| parent | d9fd363a6cbfae24ffaa00ac6fd3ce8e271acaf1 (diff) | |
| download | linux-76e4ad09a30cfb589eb436ad067f4abecb82cc04.tar.xz | |
nvme: Fix APST comment
There was a typo in the description of the timeout heuristic.
Signed-off-by: Andy Lutomirski <luto@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'drivers/nvme')
| -rw-r--r-- | drivers/nvme/host/core.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c index bf6729b1d8bf..30446e29dbd9 100644 --- a/drivers/nvme/host/core.c +++ b/drivers/nvme/host/core.c @@ -1325,7 +1325,7 @@ static void nvme_configure_apst(struct nvme_ctrl *ctrl) * heuristic: we are willing to spend at most 2% of the time * transitioning between power states. Therefore, when running * in any given state, we will enter the next lower-power - * non-operational state after waiting 100 * (enlat + exlat) + * non-operational state after waiting 50 * (enlat + exlat) * microseconds, as long as that state's total latency is under * the requested maximum latency. * |