From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH] nvme: determine the number of IO queues
Date: Thu, 18 Apr 2019 22:58:35 +0900 [thread overview]
Message-ID: <ffd4d3a7-3cfc-b69d-6045-12fdb6622f8d@gmail.com> (raw)
In-Reply-To: <38bc8924-e553-70d7-c91d-b6c864379b43@canonical.com>
On 4/18/19 10:38 PM, Aaron Ma wrote:
>
>
> On 4/18/19 9:33 PM, Minwoo Im wrote:
>> If the controller returns error for that command, how can we assure that
>> the controller would support a single I/O queue ?
>
> Make sense, I will keep *count = 0 in V2.
IMHO, If you would like to set *count to 0, then what's gonna be V2?
I guess if some device is failed, we can make it as a quirk.
>
> Thanks,
> Aaron
>
WARNING: multiple messages have this Message-ID (diff)
From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Aaron Ma <aaron.ma@canonical.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
keith.busch@intel.com, axboe@fb.com
Subject: Re: [PATCH] nvme: determine the number of IO queues
Date: Thu, 18 Apr 2019 22:58:35 +0900 [thread overview]
Message-ID: <ffd4d3a7-3cfc-b69d-6045-12fdb6622f8d@gmail.com> (raw)
In-Reply-To: <38bc8924-e553-70d7-c91d-b6c864379b43@canonical.com>
On 4/18/19 10:38 PM, Aaron Ma wrote:
>
>
> On 4/18/19 9:33 PM, Minwoo Im wrote:
>> If the controller returns error for that command, how can we assure that
>> the controller would support a single I/O queue ?
>
> Make sense, I will keep *count = 0 in V2.
IMHO, If you would like to set *count to 0, then what's gonna be V2?
I guess if some device is failed, we can make it as a quirk.
>
> Thanks,
> Aaron
>
next prev parent reply other threads:[~2019-04-18 13:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 14:12 [PATCH] nvme: determine the number of IO queues Aaron Ma
2019-04-17 14:12 ` Aaron Ma
2019-04-17 17:32 ` Maxim Levitsky
2019-04-17 17:32 ` Maxim Levitsky
2019-04-17 17:33 ` Maxim Levitsky
2019-04-17 17:33 ` Maxim Levitsky
2019-04-18 6:21 ` Aaron Ma
2019-04-18 6:21 ` Aaron Ma
2019-04-18 7:25 ` Maxim Levitsky
2019-04-18 7:25 ` Maxim Levitsky
2019-04-18 12:13 ` Minwoo Im
2019-04-18 12:13 ` Minwoo Im
2019-04-18 12:52 ` Aaron Ma
2019-04-18 12:52 ` Aaron Ma
2019-04-18 13:33 ` Minwoo Im
2019-04-18 13:33 ` Minwoo Im
2019-04-18 13:38 ` Aaron Ma
2019-04-18 13:38 ` Aaron Ma
2019-04-18 13:58 ` Minwoo Im [this message]
2019-04-18 13:58 ` Minwoo Im
2019-04-18 13:48 ` Keith Busch
2019-04-18 13:48 ` Keith Busch
2019-04-18 14:21 ` Aaron Ma
2019-04-18 14:21 ` Aaron Ma
2019-04-25 14:39 ` Christoph Hellwig
2019-04-25 14:39 ` Christoph Hellwig
2019-04-26 5:27 ` Aaron Ma
2019-04-26 5:27 ` Aaron Ma
2019-04-17 21:30 ` Edmund Nadolski (Microsoft)
2019-04-17 21:30 ` Edmund Nadolski (Microsoft)
2019-04-18 6:24 ` Aaron Ma
2019-04-18 6:24 ` Aaron Ma
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=ffd4d3a7-3cfc-b69d-6045-12fdb6622f8d@gmail.com \
--to=minwoo.im.dev@gmail.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 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.