From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, Martin.Belanger@dell.com
Subject: Re: [PATCH 2/2] nvme: don't set iosqes,iocqes for discovery controllers
Date: Wed, 24 Feb 2021 10:08:14 +0100 [thread overview]
Message-ID: <20210224090814.GA4721@lst.de> (raw)
In-Reply-To: <a5ea738a-44c4-e953-3271-a0b97668000e@grimberg.me>
On Thu, Feb 11, 2021 at 11:44:44AM -0800, Sagi Grimberg wrote:
> So you suggest that we keep the retry w.a. but continue to send the
> wrong value in 1.3 or lower?
>
> I personally think that this would be extremely confusing to users, if
> they do trip on this, but I agree that they are less likely to hit
> it because existing controllers obviously accept wrong values...
Yes. While I'd like to move to standards compliance as much as possible,
introducing a long delay for every existing working setup is
very counter productive.
>
> As for option to override. I really hate it.. What is the least exposure
> we can get for this but still allow the user to control this?
We can of course still override it using an option.
> Wish we had a good and reliable quirk mechanism for fabrics...
We do, using the serial number. But that does not help for an issue
during connection establishment.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-02-24 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 10:12 [PATCH 1/2] nvmet: don't check iosqes, iocqes for discovery controllers Sagi Grimberg
2021-02-09 10:12 ` [PATCH 2/2] nvme: don't set iosqes,iocqes " Sagi Grimberg
2021-02-10 10:11 ` Christoph Hellwig
2021-02-10 22:37 ` Sagi Grimberg
2021-02-11 7:02 ` Christoph Hellwig
2021-02-11 10:43 ` Sagi Grimberg
2021-02-11 18:31 ` Christoph Hellwig
2021-02-11 19:44 ` Sagi Grimberg
2021-02-24 9:08 ` Christoph Hellwig [this message]
2021-02-10 10:10 ` [PATCH 1/2] nvmet: don't check " Christoph Hellwig
2021-02-10 22:34 ` Sagi Grimberg
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=20210224090814.GA4721@lst.de \
--to=hch@lst.de \
--cc=Martin.Belanger@dell.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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