From: David Gibson <dgibson@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, danielhb@linux.vnet.ibm.com,
eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] scsi-disk: Don't enlarge min_io_size to max_io_size
Date: Mon, 9 Apr 2018 11:08:44 +1000 [thread overview]
Message-ID: <20180409110844.0a5188af@umbus.fritz.box> (raw)
In-Reply-To: <b00ba0ab-538f-a6f1-3b99-1a0d9adb6eab@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Thu, 5 Apr 2018 17:54:00 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 27/03/2018 18:41, Fam Zheng wrote:
> > Some backends report big max_io_sectors. Making min_io_size the same
> > value in this case will make it impossible for guest to align memory,
> > therefore the disk may not be usable at all.
> >
> > Do not enlarge them when they are zero.
> >
> > Reported-by: David Gibson <dgibson@redhat.com>
> > Signed-off-by: Fam Zheng <famz@redhat.com>
[snip]
> Queued, thanks.
>
> Paolo
Any ETA on going from queued to actually merged? This is holding up a
handful of Power bugfixes for 2.12, because I can't complete my usual
testing cycle.
--
David Gibson <dgibson@redhat.com>
Principal Software Engineer, Virtualization, Red Hat
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-09 1:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 16:41 [Qemu-devel] [PATCH v2] scsi-disk: Don't enlarge min_io_size to max_io_size Fam Zheng
2018-03-27 17:05 ` Daniel Henrique Barboza
2018-03-28 2:37 ` David Gibson
2018-04-05 15:54 ` Paolo Bonzini
2018-04-09 1:08 ` David Gibson [this message]
2018-04-09 9:28 ` Paolo Bonzini
2018-04-10 0:51 ` David Gibson
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=20180409110844.0a5188af@umbus.fritz.box \
--to=dgibson@redhat.com \
--cc=danielhb@linux.vnet.ibm.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=pbonzini@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).