All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
	pbonzini@redhat.com, benh@kernel.crashing.org
Cc: lvivier@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 08:25:34 +0200	[thread overview]
Message-ID: <55EFD0DE.1050001@redhat.com> (raw)
In-Reply-To: <1441761736-32030-1-git-send-email-david@gibson.dropbear.id.au>

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?

> 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?

 Thomas

  parent reply	other threads:[~2015-09-09  6:25 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 ` Thomas Huth [this message]
2015-09-09  7:19   ` [Qemu-devel] [PATCH] spapr: Reduce advertised max LUNs for spapr_vscsi David Gibson
2015-09-09  7:29     ` Thomas Huth
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=55EFD0DE.1050001@redhat.com \
    --to=thuth@redhat.com \
    --cc=benh@kernel.crashing.org \
    --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.