qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] virtio-scsi wiki feature page
Date: Thu, 27 Oct 2011 13:18:36 +0100	[thread overview]
Message-ID: <CAJSP0QUn50hSg7JRY7Rsdf2Eg2dwz6=a3Gk_U85PhAygwmUCfg@mail.gmail.com> (raw)
In-Reply-To: <4EA93E53.3090302@redhat.com>

On Thu, Oct 27, 2011 at 12:19 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 10/27/2011 12:49 PM, Stefan Hajnoczi wrote:
>>
>> I have created a virtio-scsi wiki feature page with links to Paolo's
>> latest draft specification, our KVM Forum presentation, and code
>> repos:
>>
>> http://wiki.qemu.org/Features/VirtioSCSI
>>
>> Paolo: v3 had some comments, is it a good time for a new revision of
>> the draft specification?
>
> Yes.  I was waiting until I actually have an implementation, but anyway here
> it is, attached.  The changes are small:
>
> - additional failure kinds mapping more or less to Linux driver_statuses
>
> - defined the format of the LUN.  Unlike vSCSI, there's no support for
> generic hierarchical LUNs.  A single LUN format is specified, that supports
> 256 targets and 16384 LUNs per target.
>
> - clarified multiqueue semantics
>
> I'm planning to update your LLD code to support these changes, but I'll
> gladly accept that someone else does it. :)

Okay, that sounds great.  As I get back into virtio-scsi I'll let you
know so we don't duplicate work.

Stefan

      reply	other threads:[~2011-10-27 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 10:49 [Qemu-devel] virtio-scsi wiki feature page Stefan Hajnoczi
2011-10-27 11:19 ` Paolo Bonzini
2011-10-27 12:18   ` Stefan Hajnoczi [this message]

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='CAJSP0QUn50hSg7JRY7Rsdf2Eg2dwz6=a3Gk_U85PhAygwmUCfg@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=pbadari@us.ibm.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).