From: Nilay Shroff <nilay@linux.ibm.com>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: kbusch@kernel.org, linux-nvme@lists.infradead.org, hch@lst.de,
sagi@grimberg.me, gjoyce@linux.ibm.com, axboe@fb.com
Subject: Re: [PATCH v3 1/1] nvme-pci : Fix EEH failure on ppc after subsystem reset
Date: Wed, 12 Jun 2024 22:37:56 +0530 [thread overview]
Message-ID: <d9d64808-397e-49ba-9f03-e9a8e773d135@linux.ibm.com> (raw)
In-Reply-To: <CAFL455kRzW25EB+89dWBMV608PyDVEfuM0Re1q69gXKZ3Uc=mg@mail.gmail.com>
On 6/12/24 18:40, Maurizio Lombardi wrote:
> st 12. 6. 2024 v 13:07 odesílatel Nilay Shroff <nilay@linux.ibm.com> napsal:
>> I think for your case you shall consider using nvme_wait_reset() before
>> queuing error recovery work. For instance, it could be done something
>> like below assuming that all callers of nvme_tcp_error_recovery() are
>> allowed to sleep (not fully tested) :
>>
>> static void nvme_tcp_error_recovery(struct nvme_ctrl *ctrl)
>> {
>> if (!nvme_wait_reset(ctrl))
>> return;
>
> Nice idea but in this case I don't think it can work
> because socket's callbacks run in interrupt context.
>
Ok so in that case how about calling nvme_wait_reset()
from nvme_tcp_error_recovery_work()?
Thanks,
--Nilay
next prev parent reply other threads:[~2024-06-12 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 9:10 [PATCH v3 0/1] nvme-pci: recover from NVM subsystem reset Nilay Shroff
2024-06-04 9:10 ` [PATCH v3 1/1] nvme-pci : Fix EEH failure on ppc after " Nilay Shroff
2024-06-10 12:32 ` Maurizio Lombardi
2024-06-12 11:07 ` Nilay Shroff
2024-06-12 13:10 ` Maurizio Lombardi
2024-06-12 17:07 ` Nilay Shroff [this message]
2024-06-13 7:02 ` Maurizio Lombardi
2024-06-14 9:51 ` Hannes Reinecke
2024-06-21 16:37 ` Keith Busch
2024-06-22 15:07 ` Nilay Shroff
2024-06-24 16:07 ` Keith Busch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d9d64808-397e-49ba-9f03-e9a8e773d135@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@fb.com \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@redhat.com \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.