From: Paolo Bonzini <pbonzini@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Alexander Graf <agraf@suse.de>,
Stefan Haynoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] megasas: LSI Megaraid SAS emulation
Date: Mon, 04 Jul 2011 08:34:37 +0200 [thread overview]
Message-ID: <4E115EFD.7020607@redhat.com> (raw)
In-Reply-To: <4E115A21.8010003@suse.de>
On 07/04/2011 08:13 AM, Hannes Reinecke wrote:
> On 07/03/2011 04:36 PM, Paolo Bonzini wrote:
>> On 07/02/2011 03:50 PM, Hannes Reinecke wrote:
>>> (And no, I will not getting into another dog-fight with Paul B. here.
>>> Virtio can do without bounce buffers. AHCI can. So I fail to see why
>>> SCSI has to rely on bounce buffers.)
>>
>> I agree, but I do see why a SCSI device might prefer to rely on
>> bounce buffers for non-I/O commands. This is why in my last RFC
>> series for vmw_pvscsi I let the device choose whether to force a
>> bounce buffer or get an external iovec from the HBA.
>>
> Yes, sure, for non-I/O commands it's perfectly okay.
> Most of which will be emulated anyway.
> It's bounce buffers for I/O which kills performance.
>
> But I seem to have missed your last RFC (I'm not reading qemu-devel on a
> regular basis ...).
> Care to send me a pointer to it?
Sure, http://lists.gnu.org/archive/html/qemu-devel/2011-06/msg00668.html
Paolo
next prev parent reply other threads:[~2011-07-04 6:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 15:35 [Qemu-devel] [PATCH 0/3] [v5] Megasas HBA Emulation Hannes Reinecke
2011-07-01 15:35 ` [Qemu-devel] [PATCH 1/3] iov: Update parameter usage in iov_(to|from)_buf() Hannes Reinecke
2011-07-01 15:35 ` [Qemu-devel] [PATCH 2/3] scsi: Add 'hba_private' to SCSIRequest Hannes Reinecke
2011-07-01 15:35 ` [Qemu-devel] [PATCH 3/3] megasas: LSI Megaraid SAS emulation Hannes Reinecke
2011-07-01 16:42 ` Alexander Graf
2011-07-02 13:50 ` Hannes Reinecke
2011-07-02 12:28 ` Alexander Graf
2011-07-03 14:36 ` Paolo Bonzini
2011-07-04 6:13 ` Hannes Reinecke
2011-07-04 6:34 ` Paolo Bonzini [this message]
2011-07-04 7:26 ` Hannes Reinecke
2011-07-04 10:29 ` Paolo Bonzini
2011-07-04 12:52 ` Hannes Reinecke
2011-07-04 12:56 ` Paolo Bonzini
2011-07-02 16:14 ` Stefan Hajnoczi
2011-07-04 8:37 ` Hannes Reinecke
2011-07-01 15:57 ` [Qemu-devel] [PATCH 2/3] scsi: Add 'hba_private' to SCSIRequest Paolo Bonzini
2011-07-01 16:19 ` [Qemu-devel] [PATCH 1/3] iov: Update parameter usage in iov_(to|from)_buf() Alexander Graf
-- strict thread matches above, loose matches on Subject: below --
2011-07-01 7:42 [Qemu-devel] [PATCH 0/3] [v4] Megasas HBA emulation Hannes Reinecke
2011-07-01 7:42 ` [Qemu-devel] [PATCH 1/3] iov: Add 'offset' parameter to iov_to_buf() Hannes Reinecke
2011-07-01 7:42 ` [Qemu-devel] [PATCH 2/3] scsi: replace 'tag' with 'hba_private' pointer Hannes Reinecke
2011-07-01 7:42 ` [Qemu-devel] [PATCH 3/3] megasas: LSI Megaraid SAS emulation Hannes Reinecke
2011-07-01 9:16 ` Alexander Graf
2011-07-03 8:09 ` Michael S. Tsirkin
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=4E115EFD.7020607@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=hare@suse.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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 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).