From: Ming Lin <mlin@kernel.org>
To: linux-rdma@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>
Cc: Bart Van Assche <bart.vanassche@sandisk.com>,
target-devel <target-devel@vger.kernel.org>
Subject: Re: iSER multi-queue configuration
Date: Fri, 29 Apr 2016 23:13:56 -0700 [thread overview]
Message-ID: <1461996836.4373.5.camel@kernel.org> (raw)
In-Reply-To: <CAF1ivSa24Y114s0f0g74jgmP8MuPfrfU_uAA7AAVR8Tsz=+avg@mail.gmail.com>
On Fri, 2016-04-29 at 14:11 -0700, Ming Lin wrote:
> Hi,
>
> I use mlx5 to setup iSER and have scsi mq enabled.
>
> root@xxx:~# cat /sys/module/scsi_mod/parameters/use_blk_mq
> Y
>
> But it seems there is only 1 HW queue that maps to 48 SW queues.
>
> root@xxx:/sys/block/sdb/mq# ls
> 0
>
> root@xxx:/sys/block/sdb/mq# ls 0/
> active cpu1 cpu11 cpu13 cpu15 cpu17 cpu19 cpu20 cpu22 cpu24
> cpu26 cpu28 cpu3 cpu31 cpu33 cpu35 cpu37 cpu39 cpu40 cpu42
> cpu44 cpu46 cpu5 cpu7 cpu9 dispatched pending run
> cpu0 cpu10 cpu12 cpu14 cpu16 cpu18 cpu2 cpu21 cpu23 cpu25
> cpu27 cpu29 cpu30 cpu32 cpu34 cpu36 cpu38 cpu4 cpu41 cpu43
> cpu45 cpu47 cpu6 cpu8 cpu_list io_poll queued tags
>
> How to configure it that I can have 48 HW queues?
> That is 1 HW queue map to 1 SW queue.
Hi Sagi,
I'm looking at why there is only 1 HW queue for iser.
2185 int scsi_mq_setup_tags(struct Scsi_Host *shost)
2186 {
...
2199 shost->tag_set.nr_hw_queues = shost->nr_hw_queues ? : 1;
It seems because iser code does not set shost->nr_hw_queues at all.
Why?
next prev parent reply other threads:[~2016-04-30 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 21:11 iSER multi-queue configuration Ming Lin
2016-04-30 6:13 ` Ming Lin [this message]
[not found] ` <1461996836.4373.5.camel-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-05-01 2:53 ` Sagi Grimberg
[not found] ` <57256FB6.7030607-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2016-05-01 6:07 ` Ming Lin
2016-05-02 15:12 ` Steve Wise
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=1461996836.4373.5.camel@kernel.org \
--to=mlin@kernel.org \
--cc=bart.vanassche@sandisk.com \
--cc=linux-rdma@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=target-devel@vger.kernel.org \
/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 NNTP newsgroup(s).