diff options
| author | James Smart <jsmart2021@gmail.com> | 2018-06-12 16:28:24 -0700 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2018-07-23 09:35:13 +0200 |
| commit | 230f1f9e04e2abee34b1478b3bcc2d947b7cc2a0 (patch) | |
| tree | bacba46ff1c9cdaca1b9b3de5f3bc9fc46503180 /drivers/nvme/target/configfs.c | |
| parent | 40c6f9c28ef03f2f2c3ee58c2447a6e6b9a713f2 (diff) | |
| download | talos-op-linux-230f1f9e04e2abee34b1478b3bcc2d947b7cc2a0.tar.gz talos-op-linux-230f1f9e04e2abee34b1478b3bcc2d947b7cc2a0.zip | |
nvme: move init of keep_alive work item to controller initialization
Currently, the code initializes the keep alive work item whenever
nvme_start_keep_alive() is called. However, this routine is called
several times while reconnecting, etc. Although it's hoped that keep
alive is always disabled and not scheduled when start is called,
re-initing if it were scheduled or completing can have very bad
side effects. There's no need for re-initialization.
Move the keep_alive work item and cmd struct initialization to
controller init.
Signed-off-by: James Smart <james.smart@broadcom.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/nvme/target/configfs.c')
0 files changed, 0 insertions, 0 deletions
