lkml.org 
[lkml]   [2006]   [Mar]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC PATCH 35/35] Add Xen virtual block device driver.
    Dave C Boutcher wrote:
    > Jeff Garzik wrote:
    >> 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? :)
    >
    > Actually SRP (which T10 has now stopped working on) fits the bill very
    > nicely.
    >

    Does the IBM vscsi code/SPEC follow the SRP SPEC or is it slightly
    modified? We also have a SRP initiator in kernel now too. It is just not
    in the drivers/scsi dir.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-03-24 20:08    [W:3.585 / U:0.496 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site