From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-scsi@vger.kernel.org, Jens Axboe <axboe@fb.com>,
linux-block@vger.kernel.org, Omar Sandoval <osandov@fb.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
James Bottomley <james.bottomley@hansenpartnership.com>,
Christoph Hellwig <hch@lst.de>,
Don Brace <don.brace@microsemi.com>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Mike Snitzer <snitzer@redhat.com>, Hannes Reinecke <hare@suse.de>,
Laurence Oberman <loberman@redhat.com>,
Bart Van Assche <bart.vanassche@wdc.com>
Subject: Re: [PATCH V2 0/2] scsi: scsi-mq: don't hold host_busy in IO path
Date: Tue, 26 Jun 2018 12:53:44 -0400 [thread overview]
Message-ID: <yq1o9fx32w7.fsf@oracle.com> (raw)
In-Reply-To: <20180624140327.28146-1-ming.lei@redhat.com> (Ming Lei's message of "Sun, 24 Jun 2018 22:03:25 +0800")
Ming,
> This patches removes the expensive atomic opeation on host-wide
> counter of .host_busy for scsi-mq, and it is observed that IOPS can be
> increased by 15% with this change in IO test over scsi_debug.
Applied to 4.19/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-06-26 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 14:03 [PATCH V2 0/2] scsi: scsi-mq: don't hold host_busy in IO path Ming Lei
2018-06-24 14:03 ` [PATCH V2 1/2] scsi: read host_busy via scsi_host_busy() Ming Lei
2018-06-25 15:37 ` Bart Van Assche
2018-06-24 14:03 ` [PATCH V2 2/2] scsi: avoid to hold host-wide counter of host_busy for scsi_mq Ming Lei
2018-06-25 15:38 ` Bart Van Assche
2018-06-29 16:20 ` [V2, " Guenter Roeck
2018-06-30 1:12 ` Ming Lei
2018-06-30 1:30 ` Ming Lei
2018-06-30 1:41 ` Guenter Roeck
2018-06-26 16:53 ` Martin K. Petersen [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=yq1o9fx32w7.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@fb.com \
--cc=bart.vanassche@wdc.com \
--cc=don.brace@microsemi.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=snitzer@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