From: John Garry <john.garry@huawei.com>
To: Hannes Reinecke <hare@suse.de>,
Bart Van Assche <bart.vanassche@sandisk.com>,
hch@infradead.org,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "zhangfei.gao@linaro.org" <zhangfei.gao@linaro.org>
Subject: Re: scsi-mq performance check
Date: Fri, 18 Dec 2015 16:50:46 +0000 [thread overview]
Message-ID: <56743966.5010309@huawei.com> (raw)
In-Reply-To: <56742EC2.2020606@suse.de>
>> We have to lock due to how we reserve a slot in the delivery queue.
>> We are looking to optimise this, but it's not straightforward.
>>
>> Perf is a good strategy, but, to be honest, I have not spent a lot
>> of time looking at this so I'm looking for low hanging fruit initially.
>>
>> FYI, our hardware does have the same number of delivery and
>> completion queues (32), and 16 cores. One thing to note is that a
>> command which was sent on queue x is not quaranteed to complete on
>> queue y.
>>
> ... then don't bother looking at scsi-mq. That is the very thing it
> relies on ...
>
> Time to change the firmware?
>
> Cheers,
>
> Hannes
Hi,
Even though a slot delivered on queue x is not guaranteed to complete on
completion queue x, is nearly always does (I just quickly tested on our
new chip, and 100% of the time it is the same - I need to check with our
hardware guys if this was only v1 of the IP).
As for firmware, our controller does not have any.
cheers,
prev parent reply other threads:[~2015-12-18 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 14:58 scsi-mq performance check John Garry
2015-12-18 15:08 ` Hannes Reinecke
2015-12-18 15:19 ` Bart Van Assche
2015-12-18 15:36 ` John Garry
2015-12-18 16:05 ` Hannes Reinecke
2015-12-18 16:50 ` John Garry [this message]
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=56743966.5010309@huawei.com \
--to=john.garry@huawei.com \
--cc=bart.vanassche@sandisk.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=zhangfei.gao@linaro.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 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.