Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Apr 2004 23:05:25 -0700 (PDT)
From:      Nate Lawson <nate@root.org>
To:        Paul Saab <ps@FreeBSD.org>
Cc:        cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/dev/ciss ciss.c cissreg.h cissvar.h        src/share/man/man4 ciss.4
Message-ID:  <20040416230427.F1848@root.org>
In-Reply-To: <20040416230100.5011316A4FE@hub.freebsd.org>
References:  <20040416230100.5011316A4FE@hub.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Excellent work, maintenance of our RAID drivers has been lacking as of
late.

On Fri, 16 Apr 2004, Paul Saab wrote:
> ps          2004/04/16 16:00:02 PDT
>
>   FreeBSD src repository
>
>   Modified files:
>     sys/dev/ciss         ciss.c cissreg.h cissvar.h
>     share/man/man4       ciss.4
>   Log:
>   Add support for the HP Modular Smart Array 20 & 500 storage arrays.
>   Logical volumes on these devices show up as LUNs behind another
>   controller (also known as proxy controller).  In order to issue
>   firmware commands for a volume on a proxy controller, they must be
>   targeted at the address of the proxy controller it is attached to,
>   not the Host/PCI controller.
>
>   A proxy controller is defined as a device listed in the INQUIRY
>   PHYSICAL LUNS command who's L2 and L3 SCSI addresses are zero.  The
>   corresponding address returned defines which "bus" the controller
>   lives on and we use this to create a virtual CAM bus.
>
>   A logical volume's addresses first byte defines the logical drive
>   number.  The second byte defines the bus that it is attached to
>   which corresponds to the BUS of the proxy controller's found or the
>   Host/PCI controller.
>
>   Change event notification to be handled in its own kernel thread.
>   This is needed since some events may require the driver to sleep
>   on some operations and this cannot be done during interrupt context.
>   With this change, it is now possible to create and destroy logical
>   volumes from FreeBSD, but it requires a native application to
>   construct the proper firmware commands which is not publicly
>   available.
>
>   Special thanks to John Cagle @ HP for providing remote access to
>   all the hardware and beating on the storage engineers at HP to
>   answer my questions.
>
>   Revision  Changes    Path
>   1.6       +4 -0      src/share/man/man4/ciss.4
>   1.41      +435 -124  src/sys/dev/ciss/ciss.c
>   1.7       +9 -0      src/sys/dev/ciss/cissreg.h
>   1.7       +18 -14    src/sys/dev/ciss/cissvar.h
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040416230427.F1848>