qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/2] virtio-scsi: Optimizing request allocation
Date: Tue, 16 Sep 2014 10:19:19 +0200	[thread overview]
Message-ID: <5417F287.6080303@redhat.com> (raw)
In-Reply-To: <1410852018-18025-1-git-send-email-famz@redhat.com>

Il 16/09/2014 09:20, Fam Zheng ha scritto:
> v3: Small tweak on "cmd" in 1/2 and "sreq" in 2/2.
> 
> Zeroing is relatively expensive since we have big request structures.
> VirtQueueElement (>48k!) and sense_buf (256 bytes) are two points to look at.
> 
> This visibly reduces overhead of request handling when testing with the
> unmerged "null" driver and virtio-scsi dataplane. Before, the issue is very
> obvious with perf top:
> 
> perf top -G -p `pidof qemu-system-x86_64`
> -----------------------------------------
> +  16.50%  libc-2.17.so             [.] __memset_sse2
> +   2.28%  libc-2.17.so             [.] _int_malloc
> +   2.25%  [vdso]                   [.] 0x0000000000000cd1
> +   2.02%  [kernel]                 [k] _raw_spin_lock_irqsave
> +   1.97%  libpthread-2.17.so       [.] pthread_mutex_lock
> +   1.87%  libpthread-2.17.so       [.] pthread_mutex_unlock
> +   1.81%  [kernel]                 [k] fget_light
> +   1.70%  libc-2.17.so             [.] malloc
> 
> After, the high __memset_sse2 and _int_malloc is gone:
> 
> perf top -G -p `pidof qemu-system-x86_64`
> -----------------------------------------
> +   4.20%  [kernel]                 [k] vcpu_enter_guest
> +   3.97%  [kernel]                 [k] vmx_vcpu_run
> +   2.63%  [kernel]                 [k] _raw_spin_lock_irqsave
> +   1.72%  [kernel]                 [k] native_read_msr_safe
> +   1.65%  [kernel]                 [k] __srcu_read_lock
> +   1.64%  [kernel]                 [k] _raw_spin_unlock_irqrestore
> +   1.57%  [vdso]                   [.] 0x00000000000008d8
> +   1.49%  libc-2.17.so             [.] _int_malloc
> +   1.29%  libpthread-2.17.so       [.] pthread_mutex_unlock
> +   1.26%  [kernel]                 [k] native_write_msr_safe
> 
> See the commit message of patch 2 for some fio test data.

Thanks, applied to scsi-next.

Paolo

      parent reply	other threads:[~2014-09-16  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  7:20 [Qemu-devel] [PATCH v3 0/2] virtio-scsi: Optimizing request allocation Fam Zheng
2014-09-16  7:20 ` [Qemu-devel] [PATCH v3 1/2] scsi: Optimize scsi_req_alloc Fam Zheng
2014-09-16  7:20 ` [Qemu-devel] [PATCH v3 2/2] virtio-scsi: Optimize virtio_scsi_init_req Fam Zheng
2014-09-16  8:19 ` Paolo Bonzini [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=5417F287.6080303@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=qemu-devel@nongnu.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).