linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Hoff <christian.hoff@de.ibm.com>
Cc: BORNTRAE@linux.vnet.ibm.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	mst@redhat.com, rusty@rustcorp.com.au
Subject: Re: Pe: [PATCH v5 1/3] virtio-scsi: first version
Date: Tue, 07 Feb 2012 15:28:54 +0100	[thread overview]
Message-ID: <4F313526.2050907@redhat.com> (raw)
In-Reply-To: <OFAFB86CAE.9917478D-ONC125799D.004AF231-C125799D.004CE6D2@de.ibm.com>

On 02/07/2012 02:59 PM, Christian Hoff wrote:
> Instead the format has some disadvantages:
> - It uses up 8 bytes where 3 bytes would be sufficient in order to store
> both the target ID and LUN number information
> - The format limits us to 255 target IDs. I agree that the LUN limit is
> probably more a theoretical and not a practical one, but 255 target IDs
> could become a limitation in the future.

It also provides better upwards-compatibility in case the limitations 
are actually hit.  If I had used "uint8_t target; uint16_t lun;" an 
extension would require a feature bit and a new struct.  With 8-bytes, 
you can just expand the definition.  That pretty much sums it up.

But again, I don't think the limitations are serious.  A MegaSAS header 
has room for 256 targets too, VMWare has only 15, Hyper-V has 1 (and 2 
channels, but I think that's an off-by-one), and you can always have 
multiple HBAs on the same guest.

> Nonetheless I think that virtio-scsi is a useful project and addresses
> many of the limitations imposed by virtio-block. The fact that I am still
> persisting has more to do with interest in the project rather than wanting
> to keep the code from going upstream.

No problem. :)

Paolo

  reply	other threads:[~2012-02-07 14:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06  9:51 Pe: [PATCH v5 1/3] virtio-scsi: first version Christian Hoff
2012-02-07  9:54 ` Paolo Bonzini
2012-02-07 11:10   ` Michael S. Tsirkin
2012-02-07 11:26     ` Paolo Bonzini
2012-02-07 11:56   ` Christian Borntraeger
2012-02-07 12:31     ` Paolo Bonzini
2012-02-07 13:18       ` Christian Borntraeger
2012-02-07 13:59         ` Christian Hoff
2012-02-07 14:28           ` Paolo Bonzini [this message]
2012-02-08 13:37             ` Christian Hoff
2012-02-09  9:25               ` Paolo Bonzini
2012-02-09 12:18                 ` Christian Hoff
2012-02-12 20:16                 ` James Bottomley
2012-02-12 23:41                   ` Rusty Russell
2012-02-13  7:05                   ` Christian Borntraeger
2012-02-13  7:57                     ` Dor Laor
2012-02-13 12:40                       ` Nicholas A. Bellinger
2012-02-13 12:54                         ` Dor Laor
2012-02-13 13:00                           ` Michael S. Tsirkin
2012-02-13 13:13                             ` ronnie sahlberg
2012-02-13 13:17                               ` Paolo Bonzini
2012-02-13 13:18                               ` Michael S. Tsirkin
2012-02-13 15:12                                 ` Hannes Reinecke
2012-02-13 20:42                                   ` ronnie sahlberg
2012-02-13 20:53                                     ` ronnie sahlberg
2012-02-13 22:59                                       ` Michael S. Tsirkin
2012-02-13 23:30                                         ` ronnie sahlberg
2012-02-13 23:33                                           ` Michael S. Tsirkin
2012-02-14  0:49                                             ` ronnie sahlberg
2012-02-14  1:11                                               ` Michael S. Tsirkin
2012-02-14  9:57                                                 ` Paolo Bonzini
2012-02-13 11:08                     ` Bart Van Assche
2012-02-13  9:19                   ` Paolo Bonzini
2012-02-14  0:07                     ` Rusty Russell

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=4F313526.2050907@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=BORNTRAE@linux.vnet.ibm.com \
    --cc=christian.hoff@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    /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).