Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: ran.anner@dell.com
Cc: hch@lst.de, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet: allow setting ctrl to ready without iosqes/iocqes set
Date: Tue, 4 May 2021 11:12:36 +0200	[thread overview]
Message-ID: <20210504091236.GA22900@lst.de> (raw)
In-Reply-To: <20210502153106.18970-1-ran.anner@dell.com>

On Sun, May 02, 2021 at 06:31:06PM +0300, ran.anner@dell.com wrote:
> From: Ran Anner <Ran.Anner@dell.com>
> 
> According to the spec we should fail creation of IO queues
> if iosqes or iocqes properties are not set but does not mention
> preventing from changing ctrl status to ready.
> We have seen host implementation which sets the property to 0x1
> and waits endlessly until ctrl status changes to ready.

So is that for a discovery controller?  The spec says the field shall
be read-only for them, although we don't reject writes to the property
right now.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  parent reply	other threads:[~2021-05-04  9:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 15:31 [PATCH] nvmet: allow setting ctrl to ready without iosqes/iocqes set ran.anner
2021-05-03 23:18 ` Chaitanya Kulkarni
2021-05-04  9:12 ` Christoph Hellwig [this message]
     [not found]   ` <MW2PR1901MB20756A164FC6DE36BE5D718291549@MW2PR1901MB2075.namprd19.prod.outlook.com>
     [not found]     ` <20210511163348.GA18486@lst.de>
2021-06-24 12:33       ` Anner, Ran
2021-06-30 18:50 ` 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=20210504091236.GA22900@lst.de \
    --to=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=ran.anner@dell.com \
    /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