From: Jeff Garzik <jeff@garzik.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Anthony Liguori <aliguori@us.ibm.com>,
Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
linux-kernel@vger.kernel.org, Ian Pratt <ian.pratt@xensource.com>,
ian.pratt@cl.cam.ac.uk,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC PATCH 35/35] Add Xen virtual block device driver.
Date: Fri, 24 Mar 2006 08:50:23 -0500 [thread overview]
Message-ID: <4423F91F.4060007@garzik.org> (raw)
In-Reply-To: <1143207657.2882.65.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Fri, 2006-03-24 at 08:37 -0500, Jeff Garzik wrote:
>> Jeff Garzik wrote:
>>> In fact, SCSI should make a few things easier, because the notion of
>>> host+bus topology is already present, and notion of messaging is already
>>> present, so you don't have to recreate that in a Xen block device
>>> infrastructure.
>> Another benefit of SCSI: when an IBM hypervisor in the Linux kernel
>> switched to SCSI, that allowed them to replace several drivers (virt
>> disk, virt cdrom, virt floppy?) with a single virt-SCSI driver.
> but there's a generic one for that: iSCSI
> so in theory you only need to provide a network driver then ;)
Talk about lots of overhead :)
OTOH, I bet that T10 is acting at high speed, right this second, to form
a committee, and multiple sub-committees, to standardize SCSI
transported over XenBus. SXP anyone? :)
Jeff
next prev parent reply other threads:[~2006-03-24 13:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 16:52 [RFC PATCH 35/35] Add Xen virtual block device driver Ian Pratt
2006-03-22 17:09 ` Anthony Liguori
2006-03-22 23:09 ` Jeff Garzik
2006-03-24 12:17 ` Alan Cox
2006-03-24 12:38 ` Jeff Garzik
2006-03-24 13:37 ` Jeff Garzik
2006-03-24 13:40 ` Arjan van de Ven
2006-03-24 13:50 ` Jeff Garzik [this message]
2006-03-24 15:33 ` Dave C Boutcher
2006-03-24 19:04 ` Mike Christie
2006-03-24 19:19 ` Dave C Boutcher
2006-03-25 0:32 ` FUJITA Tomonori
2006-03-25 0:47 ` Roland Dreier
2006-03-24 15:55 ` Alan Cox
2006-03-25 10:03 ` Rusty Russell
2006-03-27 10:14 ` Peter Chubb
2006-03-23 8:19 ` Arjan van de Ven
2006-03-23 9:34 ` Keir Fraser
2006-03-23 9:41 ` Arjan van de Ven
2006-03-23 9:42 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2006-05-09 8:49 [RFC PATCH 00/35] Xen i386 paravirtualization support Chris Wright
2006-05-09 7:00 ` [RFC PATCH 35/35] Add Xen virtual block device driver Chris Wright
2006-05-09 12:01 ` Christoph Hellwig
2006-03-22 6:30 [RFC PATCH 00/35] Xen i386 paravirtualization support Chris Wright
2006-03-22 6:31 ` [RFC PATCH 35/35] Add Xen virtual block device driver Chris Wright
2006-03-22 16:39 ` Anthony Liguori
2006-03-22 16:54 ` Christoph Hellwig
2006-03-27 8:42 ` Gerd Hoffmann
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=4423F91F.4060007@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=aliguori@us.ibm.com \
--cc=arjan@infradead.org \
--cc=chrisw@sous-sol.org \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=ian.pratt@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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