lkml.org 
[lkml]   [2005]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 2.6.13 5/14] sas-class: sas_discover.c Discover process (end devices)
    On 09/13/05 05:05, Douglas Gilbert wrote:
    > The technique of supporting REPORT_LUNS on lun 0 of
    > a target in the case where there is no such device
    > (logical unit) is a pretty ugly. It also indicates what
    > is really happening: the target device intercepts
    > REPORT_LUNS, builds the response and replies on behalf
    > of lun 0.
    >
    > Turns out there are other reasons an application may want
    > to "talk" to a target device rather than one of its logical
    > units (e.g. access controls and log pages specific to
    > the target's transport). Well known lus can be seen with the
    > REPORT_LUNS (select_report=1) but there is no mechanism (that
    > I am aware of) that allows anyone to access them
    > from the user space with linux.
    >
    >
    > References at www.t10.org:
    > spc4r01a.pdf [section 8]
    > bcc-r00.pdf [bridge controller commands]

    Well, I'm certainly glad that Doug is getting involved
    and on a SCSI professional level (quoting specs etc.).

    We need more SAM (SCSI-3) expertise in linux-scsi and
    linux-kernel.

    Luben
    -
    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: 2005-09-13 15:14    [W:2.693 / U:0.056 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site