All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: [Qemu-devel] [PATCH 1/1] iscsi: add iSCSI block device support
Date: Wed, 24 Nov 2010 18:04:37 +0100	[thread overview]
Message-ID: <20101124170437.GG31124@lst.de> (raw)
In-Reply-To: <AANLkTinke0r_ub4aqhbzG=LUjrvb4xEyM=5xFQwi1C3h@mail.gmail.com>

I don't really see the point of this.  It's implemented as a protocol,
and thus the bottom of the qemu protocol stack.  So we might get SCSI
commands in from the guest, decode them, just to re-encode them again
and send them off to the network all inside qemu.

Do you have any performance numbers showing why the addition of the
code is nessecary over just using the kernel iscsi initiator?  Which
btw, is a lot more flexible as it also supports SG_IO passthrough
and thus accessing other devices not supporting the SBC command set.

  parent reply	other threads:[~2010-11-24 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 22:17 [Qemu-devel] [PATCH 1/1] iscsi: add iSCSI block device support ronnie sahlberg
2010-11-21 23:13 ` FUJITA Tomonori
2010-11-21 23:39   ` ronnie sahlberg
2010-11-22  9:27 ` [Qemu-devel] " Kevin Wolf
2010-11-24 17:04 ` Christoph Hellwig [this message]
2010-11-24 19:14   ` [Qemu-devel] " Stefan Hajnoczi
2010-11-25  4:32     ` Nicholas A. Bellinger
2010-11-25  5:22       ` ronnie sahlberg
2010-11-25  9:30         ` Kevin Wolf

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=20101124170437.GG31124@lst.de \
    --to=hch@lst.de \
    --cc=hare@suse.de \
    --cc=kwolf@redhat.com \
    --cc=nab@linux-iscsi.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.