All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] virtio-scsi: fix parsing of hotplug/hot-unplug LUN number
Date: Thu, 26 Jul 2012 15:31:00 +0400	[thread overview]
Message-ID: <1343302260.3115.33.camel@dabdike> (raw)
In-Reply-To: <50111F6C.7010502@redhat.com>

On Thu, 2012-07-26 at 12:43 +0200, Paolo Bonzini wrote:
> Il 26/07/2012 12:33, James Bottomley ha scritto:
> >> > Has it already been considered to modify scsilun_to_int() such that LUN
> >> > numbers start at zero even for addressing method 1 ? This is what e.g.
> >> > the function scst_unpack_lun() already does. See also
> >> > http://scst.svn.sourceforge.net/viewvc/scst/trunk/scst/src/scst_lib.c?revision=HEAD&view=markup.
> > Yes, as I said before, the problem is that the actual numbers are
> > 
> > 1. not 1:1: there are several possible encodings of luns 0-255
> > 2. hierarchical, so once you go beyond a single level you can't properly
> > use a numeric representation either.
> > 
> > the mid layer just uses the lun number as an encoding of the actual SAM
> > lun.  The key for us is that int_to_scsilun has to go back the other
> > way.
> 
> I still disagree, but I will modify QEMU so that this patch is not
> necessary.  Later I can switch to int_to_scsilun.

Thanks, on the principle of least surprise, you definitely don't want
the lun numbering to change depending on whether you directly attach to
the array or pass it through virtio-scsi.

James

  reply	other threads:[~2012-07-26 11:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 16:05 [PATCH 0/2] virtio-scsi event changes for 3.6 Paolo Bonzini
2012-07-16 16:05 ` [PATCH 1/2] virtio-scsi: fix parsing of hotplug/hot-unplug LUN number Paolo Bonzini
2012-07-26  8:52   ` James Bottomley
2012-07-26  9:04     ` Paolo Bonzini
2012-07-26  9:21       ` James Bottomley
2012-07-26  9:27         ` Paolo Bonzini
2012-07-26  9:41           ` James Bottomley
2012-07-26  9:58             ` Paolo Bonzini
2012-07-26 10:17         ` Bart Van Assche
2012-07-26 10:33           ` James Bottomley
2012-07-26 10:43             ` Paolo Bonzini
2012-07-26 11:31               ` James Bottomley [this message]
2012-07-16 16:05 ` [PATCH 2/2] virtio-scsi: support online resizing of disks 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=1343302260.3115.33.camel@dabdike \
    --to=james.bottomley@hansenpartnership.com \
    --cc=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pbonzini@redhat.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 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.