From: Thomas Huth <thuth@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: lvivier@redhat.com, pbonzini@redhat.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Reduce advertised max LUNs for spapr_vscsi
Date: Wed, 9 Sep 2015 09:29:18 +0200 [thread overview]
Message-ID: <55EFDFCE.2040609@redhat.com> (raw)
In-Reply-To: <20150909071934.GD17641@voom.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
On 09/09/15 09:19, David Gibson wrote:
> On Wed, Sep 09, 2015 at 08:25:34AM +0200, Thomas Huth wrote:
>> On 09/09/15 03:22, David Gibson wrote:
>>> The implementation of the PAPR paravirtual SCSI adapter currently
>>> allows up to 32 LUNs (max_lun == 31). However the adapter isn't really
>>> designed to support lots of devices - the PowerVM implementation only
>>> ever puts one disk per vSCSI controller.
>>
>> Do you know how many LUNs are advertised by PowerVM?
>
> Well, what do you mean by "advertised". AFAIK from the point of view
> of the guest, the number of LUNs is advertised per-target, not per
> controller.
I mean, what's the highest LUN number that can be seen by a guest under
PowerVM? Is it always using only one LUN per controller, or is there a
way to change the amount of LUNs? (Sorry if I ask dumb questions ... I
do not have much experience with PowerVM yet)
>>> More specifically, the Linux guest side vscsi driver (the only one we
>>> really care about) is hardcoded to allow a maximum of 8 LUNs.
>>
>> So what about changing the vscsi driver in Linux instead to support more
>> LUNs?
>
> Doesn't help for existing guests. Basically what I'm trying to
> achieve is for qemu to reject up-front configurations that are
> unlikely to actually work in the guest.
I just wonder whether it makes sense to change the guest instead. In the
future, if we ever have guests that support more LUNs than 8 (maybe some
non-Linux guests like FreeBSD?), we've got to change QEMU back again...
OTOH, since this is just a one-line fix, it's likely ok to limit this to
8 now - it's easy to revert if we ever need to, so I'm fine with that
change, I just wanted to discuss the other possibilites.
Thomas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-09-09 7:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 1:22 [Qemu-devel] [PATCH] spapr: Reduce advertised max LUNs for spapr_vscsi David Gibson
2015-09-09 3:39 ` [Qemu-devel] [PATCHEW] Series failed testing Patchew Jenkins
2015-09-09 3:57 ` Fam Zheng
2015-09-09 6:25 ` [Qemu-devel] [PATCH] spapr: Reduce advertised max LUNs for spapr_vscsi Thomas Huth
2015-09-09 7:19 ` David Gibson
2015-09-09 7:29 ` Thomas Huth [this message]
2015-09-09 12:09 ` Paolo Bonzini
2015-09-10 1:24 ` David Gibson
2015-09-10 6:12 ` Thomas Huth
2015-09-10 6:48 ` David Gibson
2015-09-10 10:31 ` Laurent Vivier
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=55EFDFCE.2040609@redhat.com \
--to=thuth@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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.