qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Paul Brook <paul@codesourcery.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	aliguori@linux.ibm.com, kvm@vger.kernel.org,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4] Reallocate dma buffers in read/write path if needed
Date: Sun, 05 Oct 2008 07:29:17 +0200	[thread overview]
Message-ID: <48E850AD.8080904@redhat.com> (raw)
In-Reply-To: <20081004214700.GH31395@us.ibm.com>

Ryan Harper wrote:
> I'd rather avoid any additional accounting overhead of a pool.

The accounting overhead is noise compared to copying hundreds of 
megabytes per second.


> If 4MB
> is a reasonable limit, lets make that the new max.  

The real max is the dma buffer size multiplied by the number of 
concurrent requests.  With a queue depth of 64, the buffers become 4 MB 
* 64 = 256 MB.  That can double the size of a small guest, and using 
just one disk, too.

> I can do some
> testing to see where we drop off on performance improvements.  We'd
> have a default buffer size (smaller than the previous 64, and now 128k
> buf size) that is used when we allocate scsi requests; scanning through
> send_command() provides a good idea of other scsi command buf usage; and
> on reads and writes, keep the capping logic we've had all along, but
> bump the max size up to something like 4MB -- or whatever tests results
> show as being ideal. 
>   

We know what the ideal is: dropping the scatter/gather buffer completely.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

  parent reply	other threads:[~2008-10-05  5:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 22:05 [Qemu-devel] [PATCH 0/4] Improve emulated scsi write performance Ryan Harper
2008-10-03 22:05 ` [Qemu-devel] [PATCH 1/4] lsi_queue_command: add dma direction parameter Ryan Harper
2008-10-03 22:05 ` [Qemu-devel] [PATCH 2/4] Refactor lsi_do_command to queue read and write ops Ryan Harper
2008-10-03 22:05 ` [Qemu-devel] [PATCH 3/4] Refactor scsi-disk layer for queue'ing writes Ryan Harper
2008-10-03 22:05 ` [Qemu-devel] [PATCH 4/4] Reallocate dma buffers in read/write path if needed Ryan Harper
2008-10-03 23:17   ` Paul Brook
2008-10-03 23:35     ` Anthony Liguori
2008-10-04  0:00       ` Paul Brook
2008-10-04 10:00       ` Avi Kivity
     [not found]         ` <20081004135749.pphehrhuw9w4gwsc@imap.linux.ibm.com>
2008-10-04 21:47           ` Ryan Harper
2008-10-04 22:22             ` Anthony Liguori
2008-10-05  5:23               ` Avi Kivity
2008-10-05 23:06               ` Ryan Harper
2008-10-06  7:27                 ` Avi Kivity
2008-10-04 23:00             ` Paul Brook
2008-10-05  5:29             ` Avi Kivity [this message]
2008-10-05 23:08 ` [Qemu-devel] [PATCH 0/4] Improve emulated scsi write performance Ryan Harper
2008-10-13 16:15   ` Ryan Harper

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=48E850AD.8080904@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@linux.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ryanh@us.ibm.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;
as well as URLs for NNTP newsgroup(s).