From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Hannes Reinecke <hare@suse.de>,
John Garry <john.garry@huawei.com>,
bart.vanassche@sandisk.com, hch@infradead.org,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: scsi-mq performance check
Date: Fri, 18 Dec 2015 16:19:31 +0100 [thread overview]
Message-ID: <56742403.7000108@sandisk.com> (raw)
In-Reply-To: <56742168.6030200@suse.de>
On 12/18/2015 04:08 PM, Hannes Reinecke wrote:
> On 12/18/2015 03:58 PM, John Garry wrote:
>> Hi,
>>
>> I have started to enable scsi-mq on the HiSilicon SAS driver.
>>
>> Are there hints/checks I should use to make sure it is configured
>> correctly/optimally? In my initial testing I have seen some
>> performance improvements, but none like what I have seen in
>> presentations.
>>
> The whole thing is build around having symmetric submit and receive
> queues, so that we can tack a send/receive queue pair to the same CPU.
> With that we can ensure that we don't have any cache invalidation, as
> the request is already in the cache for that CPU when the completion is
> recieved. _And_ we can get rid of most spinlocks as other CPUs cannot
> access our request.
>
> So make sure to have the submit and receive queues properly done, and
> ensure you don't have any global resources within your driver which
> needs to be locked. Or move access to those resources out of the fast path.
Hello John,
It's great news that you started looking into scsi-mq support :-) As
Hannes wrote, if the performance improvement is not as big as you
expected this could be caused e.g. by lock contention. Are you familiar
with the perf tool ? The perf tool can be a great help to verify whether
lock contention occurs and also which lock(s) cause it.
Bart.
next prev parent reply other threads:[~2015-12-18 15:19 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 [this message]
2015-12-18 15:36 ` John Garry
2015-12-18 16:05 ` Hannes Reinecke
2015-12-18 16:50 ` John Garry
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=56742403.7000108@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=john.garry@huawei.com \
--cc=linux-scsi@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).