linux-kernel - [PATCH 0/4] virtio-scsi performance improvements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1339599394-13880-1-git-send-email-pbonzini@redhat.com>
Date:	Wed, 13 Jun 2012 16:56:30 +0200
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-scsi@...r.kernel.org, kvm@...r.kernel.org
Subject: [PATCH 0/4] virtio-scsi performance improvements

This series reorganizes the locking in virtio-scsi, introducing separate
scatterlists for each target and "pipelining" the locks so that one
command can be queued while the other is prepared.  This improves
performance when there are multiple in-flight operations.

For example, a simple "if=/dev/sda of=/dev/null bs=128M iflag=direct"
(the source being a 10G disk, residing entirely in the host buffer cache)
improve as follows.  The additional locking does not cause any penalty
with only one dd process, while 2 simultaneous I/O operations improve
their times by 3%:

               number of simultaneous dd
                   1               2
 ----------------------------------------
 current        5.9958s        10.2640s
 patched        5.9531s         9.8663s

Times are best of 10, and taken on a 2-VCPU guest.

 drivers/scsi/virtio_scsi.c   |  226 ++++++++++++++++++++++++++++---------------
 1 file changed, 151 insertions(+), 75 deletions(-)

Paolo Bonzini (4):
  virtio-scsi: unlock during kick
  virtio-scsi: split locking per vq
  virtio-scsi: release sg_lock after add_buf
  virtio-scsi: split scatterlist per target

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/