qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel <qemu-devel@nongnu.org>,
	ronnie sahlberg <ronniesahlberg@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] block/iscsi: use 16 byte CDBs only when necessary
Date: Wed, 3 Sep 2014 13:31:17 +0100	[thread overview]
Message-ID: <20140903123117.GJ28095@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1AAAA9D6-D7FE-447C-B136-AB3F66F67D35@kamp.de>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

On Wed, Sep 03, 2014 at 10:09:21AM +0200, Peter Lieven wrote:
> 
> 
> > Am 02.09.2014 um 21:30 schrieb Peter Lieven <pl@kamp.de>:
> > 
> > Looking at the code, is it possible that not the guest is causing trouble here, but
> > multiwrite_merge code?
> > 
> > From what I see the only limit it has when merging requests is the number of IOVs.
> > 
> > 
> > Any thoughts?
> > 
> > Mine are:
> > a) Introducing bs->bl.max_request_size and set merge = 0 if the result would be too big. Default
> > max request size to 32768 sectors (see below).
> > b) Hardcoding the limit in multiwrite_merge for now limiting the merged size to 16MB (32768 sectors).
> >     Which is the limit we already use in bdrv_co_discard and bdrv_co_write_zeroes if we don't know
> >     better.
> 
> or c) disabling multiwrite merge for RAW or only iSCSI completely.

I think you're right, multiwrite could merge a larger request than the
storage device can handle.

Do you want to implement a)?

b) is okayish.  c) is too hacky and might result in performance
regressions because it changes the I/O pattern for existing guests.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-09-03 12:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 13:47 [Qemu-devel] [PATCH] block/iscsi: use 16 byte CDBs only when necessary Peter Lieven
2014-06-04 14:00 ` ronnie sahlberg
2014-06-04 14:43   ` Peter Lieven
2014-06-04 14:54     ` ronnie sahlberg
2014-06-05  9:12   ` Michael Tokarev
2014-06-05  9:27     ` Peter Lieven
2014-06-17  6:14     ` Peter Lieven
2014-06-17 11:15       ` Paolo Bonzini
2014-06-17 11:37         ` Peter Lieven
2014-06-17 11:46           ` Paolo Bonzini
2014-06-17 11:50             ` Peter Lieven
2014-06-17 13:45             ` Peter Lieven
2014-09-01 15:21             ` Peter Lieven
2014-09-02 15:28               ` ronnie sahlberg
2014-09-02 18:14                 ` Peter Lieven
2014-09-02 19:30                 ` Peter Lieven
2014-09-03  8:09                   ` Peter Lieven
2014-09-03 12:31                     ` Stefan Hajnoczi [this message]
2014-09-03 13:13                       ` Peter Lieven
2014-09-03 14:17                     ` ronnie sahlberg
2014-09-03 14:18                       ` Paolo Bonzini
2014-09-03 14:48                         ` ronnie sahlberg
2014-09-03 19:29                           ` Peter Lieven
2014-06-04 15:31 ` Paolo Bonzini

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=20140903123117.GJ28095@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.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).