From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: Nicholas Bellinger <nab@daterainc.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
qla2xxx-upstream@qlogic.com, Kent Overstreet <kmo@daterainc.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH RFC 0/2] percpu_tags: Prototype implementation
Date: Mon, 11 Aug 2014 13:52:21 -0700 [thread overview]
Message-ID: <1407790341.334.2.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <20140811201744.GD8397@lenovo-rd230-04.lab.bos.redhat.com>
(Responding again without gmail, as the last email hit a failure when
responding to the lists..)
On Mon, 2014-08-11 at 16:17 -0400, Alexander Gordeev wrote:
> On Fri, Jul 18, 2014 at 12:20:56PM +0200, Alexander Gordeev wrote:
> > The performance test is not decent, though. I used "fio" random
> > read against a "null_blk" device sitting on top of "percpu_tags",
> > which is not exactly how "percpu_ida" is used. This is another
> > reason I am posting - an advice on how to properly test is very
> > appreciated.
>
> Hi Nicholas et al,
>
> I expect the best possible performance test for percpu_ida/percpu_tags
> would be to stress drivers/vhost/scsi.c vhost_scsi_get_tag() function.
>
> I tried to make such test by attaching ramdisk to a virtual machine
> (similar to https://lkml.org/lkml/2012/8/10/347) but ultimately failed
> to configure the necessary environment - the stock qemu does not have
> -vhost-scsi parameter.
>
> Could you please advice how to make this configuration exposed to guests?
>
> o- / ..................................................................... [...]
> o- backstores .......................................................... [...]
> | o- block .............................................. [Storage Objects: 0]
> | o- fileio ............................................. [Storage Objects: 0]
> | o- pscsi .............................................. [Storage Objects: 0]
> | o- ramdisk ............................................ [Storage Objects: 1]
> | o- rda .............................................. [(1.0GiB) activated]
> o- iscsi ........................................................ [Targets: 0]
> o- loopback ..................................................... [Targets: 0]
> o- vhost ........................................................ [Targets: 1]
> o- naa.5001405b171ee405 .......................................... [TPGs: 1]
> o- tpg1 .............................. [naa.5001405983a5b1a4, no-gen-acls]
> o- acls ...................................................... [ACLs: 0]
> o- luns ...................................................... [LUNs: 1]
> o- lun0 ................................................ [ramdisk/rda]
>
So qemu expects '-device vhost-scsi-pci' with the following syntax:
-device vhost-scsi-pci,wwpn=naa.5001405b171ee405,num_queues=1,cmd_per_lun=64
For best results I'd recommend setting the IRQ affinity for each of the
virtio*_request MSI-X vectors to a dedicated vCPU in KVM guest.
Also, I've been using the scsi-mq prototype for small block I/O
performance testing in order to push vhost-scsi and avoid the legacy
scsi_request_fn() bottleneck(s) with virtio-scsi, and now that hch's
scsi-mq work (CC'ed) has been merged upstream in v3.17-rc0, it would be
a good time for a scsi-mq + virtio-scsi + vhost-scsi performance
checkpoint. ;)
--nab
next prev parent reply other threads:[~2014-08-11 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 10:20 Alexander Gordeev
2014-07-18 10:20 ` [PATCH RFC 1/2] " Alexander Gordeev
2014-07-18 10:20 ` [PATCH RFC 2/2] percpu_tags: Use percpu_tags instead of percpu_ida Alexander Gordeev
2014-08-11 20:17 ` [PATCH RFC 0/2] percpu_tags: Prototype implementation Alexander Gordeev
2014-08-11 20:52 ` Nicholas A. Bellinger [this message]
2014-08-11 20:57 ` Nicholas A. Bellinger
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=1407790341.334.2.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=agordeev@redhat.com \
--cc=hch@lst.de \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nab@daterainc.com \
--cc=qla2xxx-upstream@qlogic.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
all inboxes | Powered by JetHome®