From: Hannes Reinecke <hare@suse.de>
To: Sumit.Saxena@avagotech.com, linux-scsi@vger.kernel.org
Cc: thenzl@redhat.com, martin.petersen@oracle.com, hch@infradead.org,
jbottomley@parallels.com, kashyap.desai@avagotech.com
Subject: Re: [PATCH RESEND 6/18] megaraid_sas : Use Block layer tag support for internal command indexing
Date: Tue, 21 Apr 2015 12:26:51 +0200 [thread overview]
Message-ID: <553625EB.3060404@suse.de> (raw)
In-Reply-To: <201504201235.t3KCZWSY016519@palmhbs0.lsi.com>
On 04/20/2015 02:33 PM, Sumit.Saxena@avagotech.com wrote:
> megaraid_sas driver will use block layer provided tag for indexing internal MPT frames to get any unique MPT frame tied with tag.
> Each IO request submitted from SCSI mid layer will get associated MPT frame from MPT framepool (retrieved and return back using spinlock
> inside megaraid_sas driver's submission/completion call back). Getting MPT frame from MPT Frame pool is very expensive operation because
> of associated spin lock operation (spinlock overhead increase on multi NUMA node). This type of locking in driver is very expensive
> call considering each IO request need - Acquire and Release of the same lock.
>
> With this support, in IO path driver will directly provide the unique command index(which is based on block layer tag)
> and will get the MPT frame tied to the tag and this way driver can get rid off lock, which synchronizes the access to MPT frame pool
> while fetching and returning MPT frame from the pool.
>
> This support in driver provides siginificant performance improvement(on multi NUMA node system)on latest upstream with SCSI.MQ
> as well as on existing linux distributions.
> Here is the data for test executed at Avago-
> - IO Tool- FIO
> - 4 Socket SMC server. (4 NUMA node server)
> - 12 SSDs in JBOD mode .
> - 4K Rand READ, QD=32
> - SCSI MQ x86_64 (Latest Upstream kernel)
> - upto 300% Performance Improvement.
>
> If IOs are running on single Node, perfromance gain is less, but as soon as increase number of nodes, performance improvement
> is significant. IOs running on all 4 NUMA nodes, with this patch applied IOPs observed was 1170K vs 344K IOPs seen without this patch.
>
> Signed-off-by: Kashyap Desai <kashyap.desai@avagotech.com>
> Signed-off-by: Sumit Saxena <sumit.saxena@avagotech.com>
> ---
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-21 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 12:33 [PATCH RESEND 6/18] megaraid_sas : Use Block layer tag support for internal command indexing Sumit.Saxena
2015-04-21 10:26 ` Hannes Reinecke [this message]
2015-04-21 10:42 ` Christoph Hellwig
2015-04-21 12:33 ` Sumit Saxena
2015-04-22 11:32 ` Sumit Saxena
2015-04-22 11:40 ` Christoph Hellwig
2015-04-22 12:04 ` Sumit Saxena
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=553625EB.3060404@suse.de \
--to=hare@suse.de \
--cc=Sumit.Saxena@avagotech.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=thenzl@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 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.