From: ming.lei@redhat.com (Ming Lei)
Subject: [PATCH 2/3] nvme-pci: remove queue_count_ops for write,poll_queues
Date: Mon, 10 Jun 2019 10:41:28 +0800 [thread overview]
Message-ID: <20190610024127.GE26551@ming.t460p> (raw)
In-Reply-To: <20190610022522epcms2p26bc1b339680476ac6d81050045545f44@epcms2p2>
On Mon, Jun 10, 2019@11:25:22AM +0900, Minwoo Im wrote:
> > However, the check is valid, which shouldn't be nop, so could you fix
> > the check instead of removing it?
>
> Hi, Ming.
>
> I don't get what you really mean here. What do you mean "the check is
> valid"? I don't see any valid checks in queue_count_set(), not just for
> check for the failure by kstrtoint(). I think current code is just checks
> the nr_cpus and do nothing after.
>
> Instead fixing this check inside of this function, I have posted the next
> patch in this series to make sure the number of irqs requested not
> exceed the num_possible_num().
I suggest to cap 'write_queues' or 'poll_writes' to num_possible_num()
from the beginning, instead of starting with invalid number.
thanks,
Ming
next prev parent reply other threads:[~2019-06-10 2:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 18:02 [PATCH 0/3] nvme-pci: adjust irq max_vector to avoid WARN() Minwoo Im
2019-06-08 18:02 ` [PATCH 1/3] nvme-pci: remove unnecessary zero for static var Minwoo Im
2019-06-08 20:27 ` Chaitanya Kulkarni
2019-06-08 18:02 ` [PATCH 2/3] nvme-pci: remove queue_count_ops for write,poll_queues Minwoo Im
2019-06-10 1:51 ` Ming Lei
2019-06-10 2:25 ` Minwoo Im
2019-06-10 2:41 ` Ming Lei [this message]
2019-06-10 3:41 ` Minwoo Im
2019-06-10 3:49 ` [PATCH 2/3] nvme-pci: remove queue_count_ops for write, poll_queues Ming Lei
2019-06-10 3:52 ` Minwoo Im
2019-06-16 4:51 ` [PATCH 2/3] nvme-pci: remove queue_count_ops for write,poll_queues Minwoo Im
2019-06-20 6:25 ` Christoph Hellwig
2019-06-08 18:02 ` [PATCH 3/3] nvme-pci: adjust irq max_vector using num_possible_cpus() Minwoo Im
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=20190610024127.GE26551@ming.t460p \
--to=ming.lei@redhat.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