[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110629103139.GC16757@redhat.com>
Date: Wed, 29 Jun 2011 13:31:39 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Hannes Reinecke <hare@...e.de>,
Linux Virtualization <virtualization@...ts.linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
qemu-devel <qemu-devel@...gnu.org>,
Rusty Russell <rusty@...tcorp.com.au>,
Stefan Hajnoczi <stefanha@...ux.vnet.ibm.com>,
Christoph Hellwig <chellwig@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
Subject: Re: virtio scsi host draft specification, v3
On Wed, Jun 29, 2011 at 12:06:29PM +0200, Paolo Bonzini wrote:
> On 06/29/2011 12:03 PM, Christoph Hellwig wrote:
> >> I agree here, in fact I misread Hannes's comment as "if a driver
> >> uses more than one queue it is responsibility of the driver to
> >> ensure strict request ordering". If you send requests to different
> >> queues, you know that those requests are independent. I don't think
> >> anything else is feasible in the virtio framework.
> >
> >That doesn't really fit very well with the SAM model. If we want
> >to use multiple queues for a single LUN it has to be transparent to
> >the SCSI command stream. Then again I don't quite see the use for
> >that anyway.
>
> Agreed, I see a use for multiple queues (MSI-X), but not for
> multiple queues shared by a single LUN.
>
> Paolo
Then let's make it explicit in the spec?
--
MST
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists