[PATCHv2] nvme: send uevent once a multipath namespace is operational again
Hannes Reinecke
hare at suse.de
Wed Mar 3 13:05:19 GMT 2021
On 3/3/21 1:32 PM, Christoph Hellwig wrote:
> On Wed, Mar 03, 2021 at 01:12:27PM +0100, Hannes Reinecke wrote:
>> In an all paths down scenario I/O will be requeued or aborted, and no
>> further I/O will be ongoing on this namespace.
>> This leaves the upper layers unable to determine if the namespace
>> becomes operational again eg. after a successful controller reset.
>> With this patch a 'change' uevent will be sent per multipathed namespace
>> once the underlying controller moved to LIVE and started I/O processing
>> by calling nvme_kick_requeue_lists().
>
> This looks functionally correct, but I'm a little worried about the
> nvme_kick_requeue_lists function name being a little off now. Can
> anyone on the list think of a better name?
>
nvme_restart_processing()?
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare at suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
More information about the Linux-nvme
mailing list