qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Hellwig <chellwig@redhat.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	qemu-devel <qemu-devel@nongnu.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>,
	Linux Virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [Qemu-devel] virtio scsi host draft specification, v3
Date: Wed, 29 Jun 2011 12:06:29 +0200	[thread overview]
Message-ID: <4E0AF925.2050707@redhat.com> (raw)
In-Reply-To: <20110629100341.GC22900@infradead.org>

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

  reply	other threads:[~2011-06-29 10:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 13:43 [Qemu-devel] virtio scsi host draft specification, v3 Paolo Bonzini
2011-06-08 23:28 ` Rusty Russell
2011-06-09  6:59   ` Paolo Bonzini
2011-06-10 11:33     ` Rusty Russell
2011-06-10 12:14       ` Stefan Hajnoczi
2011-06-10 12:22         ` Paolo Bonzini
2011-06-10 12:55 ` Hannes Reinecke
2011-06-10 14:35   ` Paolo Bonzini
2011-06-14  8:39     ` Hannes Reinecke
2011-06-14 15:53       ` Stefan Hajnoczi
2011-06-29  8:33       ` Paolo Bonzini
2011-06-29  9:39         ` Stefan Hajnoczi
2011-06-29 10:07           ` Christoph Hellwig
2011-06-29 10:23             ` Hannes Reinecke
2011-06-29 10:27               ` Christoph Hellwig
2011-07-01  6:41           ` Paolo Bonzini
2011-07-01  7:14             ` Hannes Reinecke
2011-07-01  8:35               ` Paolo Bonzini
2011-07-04 13:38                 ` Hai Dong,Li
2011-07-04 14:22                   ` Stefan Hajnoczi
2011-06-12  7:51   ` Michael S. Tsirkin
2011-06-14 15:30     ` Hannes Reinecke
2011-06-29 10:00       ` Christoph Hellwig
2011-06-29  8:23     ` Paolo Bonzini
2011-06-29  8:46       ` Michael S. Tsirkin
2011-06-29 10:03       ` Christoph Hellwig
2011-06-29 10:06         ` Paolo Bonzini [this message]
2011-06-29 10:31           ` Michael S. Tsirkin
2011-06-29 10:35             ` Paolo Bonzini
2011-06-29 10:01     ` Christoph Hellwig

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=4E0AF925.2050707@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=chellwig@redhat.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=virtualization@lists.linux-foundation.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).