All of lore.kernel.org
 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 2/2] virtio-scsi: Optimize virtio_scsi_init_req
Date: Thu, 11 Sep 2014 12:55:51 +0200	[thread overview]
Message-ID: <54117FB7.6020103@redhat.com> (raw)
In-Reply-To: <1410430599-27540-3-git-send-email-famz@redhat.com>

Similar nits to patch 1, but a good patch nevertheless!

Il 11/09/2014 12:16, Fam Zheng ha scritto:
> The VirtQueueElement is a very big structure (> 4k), since it will be
> initialzed by virtqueue_pop, we can save the expensive zeroing here.
> 
> This saves a few nanoseconds per request in my test:
> 
> [fio-test]      rw         bs         iodepth    jobs       bw         iops       latency
> --------------------------------------------------------------------------------------------
> Before          read       4k         1          1          110        28269      34
> After           read       4k         1          1          131        33745      28
> 
> virtio-blk      read       4k         1          1          217        55673      16
> 
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
>  hw/scsi/virtio-scsi.c           | 17 ++++++++++-------
>  include/hw/virtio/virtio-scsi.h |  1 +
>  2 files changed, 11 insertions(+), 7 deletions(-)
> 
> diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
> index 86aba88..0792529 100644
> --- a/hw/scsi/virtio-scsi.c
> +++ b/hw/scsi/virtio-scsi.c
> @@ -24,12 +24,12 @@
>  typedef struct VirtIOSCSIReq {
>      VirtIOSCSI *dev;
>      VirtQueue *vq;
> -    VirtQueueElement elem;
>      QEMUSGList qsgl;
> +    QEMUIOVector resp_iov;
> +    VirtQueueElement elem;

Needs a comment where the zeroed section begins.

>      SCSIRequest *sreq;
>      size_t resp_size;
>      enum SCSIXferMode mode;
> -    QEMUIOVector resp_iov;
>      union {
>          VirtIOSCSICmdResp     cmd;
>          VirtIOSCSICtrlTMFResp tmf;
> @@ -44,6 +44,7 @@ typedef struct VirtIOSCSIReq {
>          VirtIOSCSICtrlTMFReq  tmf;
>          VirtIOSCSICtrlANReq   an;
>      } req;
> +    uint8_t cdb[VIRTIO_SCSI_CDB_SIZE_MAX];
>  } VirtIOSCSIReq;
>  
>  QEMU_BUILD_BUG_ON(offsetof(VirtIOSCSIReq, req.cdb) !=
> @@ -68,15 +69,16 @@ static inline SCSIDevice *virtio_scsi_device_find(VirtIOSCSI *s, uint8_t *lun)
>  static VirtIOSCSIReq *virtio_scsi_init_req(VirtIOSCSI *s, VirtQueue *vq)
>  {
>      VirtIOSCSIReq *req;
> -    VirtIOSCSICommon *vs = VIRTIO_SCSI_COMMON(s);
> -
> -    req = g_malloc0(sizeof(*req) + vs->cdb_size);
> +    const size_t zero_skip = offsetof(VirtIOSCSIReq, elem)
> +                             + sizeof(VirtQueueElement);
>  
> +    req = g_slice_new(VirtIOSCSIReq);

I would use g_slice_alloc here, and avoid zeroing the largeish cdb field.

>      req->vq = vq;
>      req->dev = s;
>      req->sreq = NULL;

This NULL initialization can be removed.

Paolo

>      qemu_sglist_init(&req->qsgl, DEVICE(s), 8, &address_space_memory);
>      qemu_iovec_init(&req->resp_iov, 1);
> +    memset((uint8_t *)req + zero_skip, 0, sizeof(*req) - zero_skip);
>      return req;
>  }
>  
> @@ -84,7 +86,7 @@ static void virtio_scsi_free_req(VirtIOSCSIReq *req)
>  {
>      qemu_iovec_destroy(&req->resp_iov);
>      qemu_sglist_destroy(&req->qsgl);
> -    g_free(req);
> +    g_slice_free(VirtIOSCSIReq, req);
>  }
>  
>  static void virtio_scsi_complete_req(VirtIOSCSIReq *req)
> @@ -532,7 +534,8 @@ static void virtio_scsi_set_config(VirtIODevice *vdev,
>      VirtIOSCSICommon *vs = VIRTIO_SCSI_COMMON(vdev);
>  
>      if ((uint32_t) virtio_ldl_p(vdev, &scsiconf->sense_size) >= 65536 ||
> -        (uint32_t) virtio_ldl_p(vdev, &scsiconf->cdb_size) >= 256) {
> +        (uint32_t) virtio_ldl_p(vdev, &scsiconf->cdb_size)
> +                   >= VIRTIO_SCSI_CDB_SIZE_MAX) {
>          error_report("bad data written to virtio-scsi configuration space");
>          exit(1);
>      }
> diff --git a/include/hw/virtio/virtio-scsi.h b/include/hw/virtio/virtio-scsi.h
> index 188a2d9..6e876f4 100644
> --- a/include/hw/virtio/virtio-scsi.h
> +++ b/include/hw/virtio/virtio-scsi.h
> @@ -37,6 +37,7 @@
>  
>  #define VIRTIO_SCSI_VQ_SIZE     128
>  #define VIRTIO_SCSI_CDB_SIZE    32
> +#define VIRTIO_SCSI_CDB_SIZE_MAX 256
>  #define VIRTIO_SCSI_SENSE_SIZE  96
>  #define VIRTIO_SCSI_MAX_CHANNEL 0
>  #define VIRTIO_SCSI_MAX_TARGET  255
> 

      reply	other threads:[~2014-09-11 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 10:16 [Qemu-devel] [PATCH 0/2] virtio-scsi: Optimizing request allocation Fam Zheng
2014-09-11 10:16 ` [Qemu-devel] [PATCH 1/2] scsi: Optimize scsi_req_alloc Fam Zheng
2014-09-11 10:52   ` Paolo Bonzini
2014-09-11 10:16 ` [Qemu-devel] [PATCH 2/2] virtio-scsi: Optimize virtio_scsi_init_req Fam Zheng
2014-09-11 10:55   ` 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=54117FB7.6020103@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 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.