From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
lsf-pc@lists.linuxfoundation.org,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: [LSF/MM/BPF TOPIC] nvme-of connect retries
Date: Wed, 8 May 2024 11:52:38 +0200 [thread overview]
Message-ID: <3545cebf-42be-4181-a370-c1ec1069d388@suse.de> (raw)
Hi all,
I'd like to request another session for LSF/MM:
NVMe-oF connect retries
There had been several discussions on the mailing list on how to handle
failures or retries which occurs during 'connect'.
Issues to discuss:
- Should the initial connect return with a status after _all_
queues are connected? That will introduce a severe lag
for large installation, with the risk of systemd timing out
the command.
- Should we try to combine workflows? TCP has three different
'connect' code paths, one for the initial connect, one for
reset, and one for reconnect.
- Where should a possible retry be handled? Should user space
be responsible for a retry, or should it be left to the driver?
- If user space should be driving the retry, how can we return
a meaningful error to user space?
It would be good if we could come to a consensus here such that
we can start consolidating the various transports.
Cheers,
Hannes
reply other threads:[~2024-05-08 9:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3545cebf-42be-4181-a370-c1ec1069d388@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).