From Cecilia.Hu@sun.com Sun Apr 19 22:00:23 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3K50NZ2025674 for ; Sun, 19 Apr 2009 22:00:23 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3K50NVZ001964 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Sun, 19 Apr 2009 22:00:23 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KID00505V8NW000@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Sun, 19 Apr 2009 22:00:23 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KID0018LV8KO080@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Sun, 19 Apr 2009 22:00:21 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3K50KY0009345 for ; Mon, 20 Apr 2009 05:00:20 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KID00000V1BKT00@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 13:00:20 +0800 (SGT) Received: from [129.158.218.98] ([unknown] [129.158.218.98]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KID009B6V8JS6E0@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 13:00:20 +0800 (SGT) Date: Mon, 20 Apr 2009 12:57:49 +0800 From: Cecilia Hu Subject: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller Sender: Cecilia.Hu@sun.com To: psarc-ext@sun.com Cc: Javen Wu , Yongfeng.Du@sun.com Reply-to: Cecilia.Hu@sun.com Message-id: <49EC00CD.4020205@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.9 (X11/20080128) Status: RO Content-Length: 7082 I am sponsoring this fast tack for Javen Wu and Dolpher Du. It is to provide a mpt_sas(7D) driver. Timer is set to 04/26, requested release binding is micro. -Cecilia -------------------------------------------------------------------- Name: Driver for LSI MPT2.0 compliant SAS 2.0 controller Submitters: Javen Wu, Dolpher Du 1) Background ------------- Over the past decade the storage industry has moved from traditional parallel SCSI based storage systems to more scalable serial storage connections. With the emergence of 3 and 6 Gigabit SAS, Sun and other vendors are revamping software storage stacks to support the new features. LSI's Fusion MPT Message Passing Technology forms the basis for a very popular family of Serial Attached SCSI HBAs. Sun makes extensive use of MPT for both PCI-E and PCI-X option cards as well as for motherboard hosted storage. The mpt(7D) driver was based on LSI's MPT v1.5, supporting both SAS and Parallel SCSI devices. LSI's support of the SAS 2.0 specification uses a new driver/firmware interface. MPT(rev2) is now under development. In order for Sun to implement those changes we need to provide a new HBA driver which does not have the legacy requirement of mpt(7D). The proposed new driver mpt_sas(7D) will drive LSI MPT2 compliant SAS controllers which include LSI SAS200x/2108 series. 2) Proposal Summary ------------------- The following features are supported by the proposed mpt_sas(7D) driver: 2.1) mpt_sas(7D) is DDI compliant and SCSA compliant as much as applicable. 2.2) SAS initiator ports registration. 2.3) SAS/SATA/SMP target device dynamic enumeration / reconfiguration. 2.4) Target device representation conforms to FWARC 2008/013. 2.5) SAS/SATA devices multipathing support. 2.6) Power management, FMA and fast reboot support. 2.7) 3rd party ioctl support for management and firmware upgrade. 3) Interface Table ------------------- |----------------------------------------------------------| | Interface Name | Classification | Comments | |------------------|------------------+--------------------| | mpt_sas(7D) | Committed | Driver name | | | | | | mpt_sas.conf | Committed | Configuration file | | | | | | SUNWmptsas | Committed | Package name | | | | | |----------------------------------------------------------| 4) Proposal Details -------------------- 4.1) mpt_sas(7D) is as a SCSI/SAS HBA driver across SPARC and x86 platforms which supports stock SCSA interfaces. 4.2) The proposed driver supports multiple initiator ports. Exporting the real SCSI I-T nexus, once mpt_sas(7D) detects initiator ports, it would register the initiator ports. These are represented as individual child nexus devinfo nodes in the Solaris device tree. All attached target devices would be children of a specific initiator port rather than PCI function. The IR (Integrated RAID) volumes are children of a special virtual initiator port nexus. 4.3) The driver class of proposed driver is "scsi-self-identifying" which means that the driver is able to discover and enumerate target devices automatically rather than relying entries in the .conf file of the target driver. The proposed driver is able to discover and enumerate SAS/SATA/SMP /IR target devices. 4.4) The propsed driver represents attached target devices in standard way which would be compatible with future SCSA v3 naming rules. 4.4.1) The node names of the SAS/SATA target devices are generic node names and based on scsi device type (dtype). 4.4.2) The unit-address of SAS/SATA target devices are the form of "target identifier, lun". The detail specification of target identifier please refer to FWARC 2008/013. The rule is generally of the form: 4.4.2.1) The target identifier of SAS target device is SAS address. 4.4.2.2) The target identifier of SATA target devices with ATA "Device Name" (108-111 words of ATA IDENTIFY) is the ATA "Device Name". 4.4.2.3) The target identifier of directly attached SATA device without ATA "Device Name" is attached PHY identifier. 4.4.2.4) The target identifier of indirectly attached SATA device without ATA "Device Name" is STP address which is assigned by expander. 4.4.3) The node name of SMP target is "smp". 4.4.4) The unit address of SMP target is SAS address. 4.4.5) The node name of IR volume is "disk". 4.4.6) The unit address of IR volume is form of "w$WWID,0". WWID of IR volume is World Wide Identifier of the IR volume by replacing the top nibble to "3". 4.5) The proposed driver supports Solaris IO Multipathing(MPxIO) for SAS/SATA devices and MPxIO is turned on by default. Solaris I/O multipathing is enabled or disabled on SAS/SATA devices which associates to mpt_sas(7D) with the mpxio-disable property. Specifying mpxio-disable="no" activates I/O multipathing, while mpxio-disable="yes" disables the feature. I/O multipathing feature of mpt_sas(7D) may be enabled or disabled on a per HBA basis. /kernel/drv/mpt_sas.conf will contain commentary about property 'mpxio-disable', system administrators will need to modify the property, or use the stmsboot(1M) utility to disable or enable MPxIO. The default setting for 'mpxio-disable' (When missing the entry), will be "no". This means that the SAS/SATA MPxIO feature will be enabled by default unless specifically disabled by the system administrator. 4.6) The proposed driver supports Power management, FMA and fast reboot as required. 4.7) The proposed driver supports some Project Private ioctl interfaces. These enable the use of a vendor utility with the mpt_sas(7D) driver. 5) Packaging & Delivery: The mpt_sas(7d) driver will be delivered initially on both x86 and SPARC architectures, the driver delivery will include: /kernel/drv/mpt_sas /kernel/drv/mpt_sas.conf /kernel/drv/amd64/mpt_sas /kernel/drv/sparcv9/mpt_sas The mpt_sas(7d) manpage will be included in SUNWman. 6). Resources and Schedule: 6.1). Product Approval Committee requested information: 6.1.1) Consolidation or Component Name: ON 6.2) ARC review type: Fast Track 6.3) ARC Exposure: open 6) References ------------- LSI MPI 2.0 revision J PSARC/2006/703 MPxIO extension for Serial Attached SCSI (SAS) on mpt(7D) PSARC/2007/595 Serial Attached SCSI (SAS) Management Protocol (SMP) support for Solaris PSARC/2008/337 scsi-self-identifying PSARC/2002/510 Sun Fire V440 (Chalupa) - Platform support [introduced MPT] PSARC/2005/097 Solaris support for LSI SAS1064 on Ontario FWARC/2008/013 SCSI SAS 1275 Binding CR 6810441 Solaris needs to expose initiator port for multiple-port HBAs CR 6762621 Add interconnect type for SAS transport. From gdamore@sun.com Mon Apr 20 08:17:47 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3KFHlWK022353 for ; Mon, 20 Apr 2009 08:17:47 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3KFHSTu010069 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Mon, 20 Apr 2009 08:17:47 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KIE00I0DNTLZ000@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 08:17:45 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIE00IL2NTKLX10@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 08:17:44 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n3KFHiqd012492 for ; Mon, 20 Apr 2009 08:17:44 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIE00E00MS85200@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 08:17:44 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIE00GEVNT2RY20@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 08:17:26 -0700 (PDT) Date: Mon, 20 Apr 2009 08:17:25 -0700 From: "Garrett D'Amore" Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49EC00CD.4020205@sun.com> Sender: Garrett.Damore@sun.com To: Cecilia.Hu@sun.com Cc: psarc-ext@sun.com, Javen Wu , Yongfeng.Du@sun.com Message-id: <49EC9205.3050607@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 7975 +1. I'd like to encourage someone in the storage team to find a better solution to configuring mpxio than the driver.conf properties. Anyone who's worked with driver.conf tunables for PCI devices knows that these are awkward and error prone, especially if you want to have individual instances of the driver with different property settings. (This problem is part of why Brussels exists for NIC drivers....) Perhaps an SMF tunable or some other system similar to Brussels would be more appropriate. - Garrett Cecilia Hu wrote: > I am sponsoring this fast tack for Javen Wu and Dolpher Du. It is to > provide a mpt_sas(7D) driver. Timer is set to 04/26, requested release > binding is micro. > > -Cecilia > > > > > -------------------------------------------------------------------- > Name: Driver for LSI MPT2.0 compliant SAS 2.0 controller > Submitters: Javen Wu, Dolpher Du > > 1) Background > ------------- > > Over the past decade the storage industry has moved from traditional > parallel > SCSI based storage systems to more scalable serial storage > connections. With > the emergence of 3 and 6 Gigabit SAS, Sun and other vendors are revamping > software storage stacks to support the new features. > > LSI's Fusion MPT Message Passing Technology forms the basis for a very > popular > family of Serial Attached SCSI HBAs. Sun makes extensive use of MPT for > both PCI-E and PCI-X option cards as well as for motherboard hosted > storage. > The mpt(7D) driver was based on LSI's MPT v1.5, supporting both SAS and > Parallel SCSI devices. > > LSI's support of the SAS 2.0 specification uses a new driver/firmware > interface. > MPT(rev2) is now under development. In order for Sun to implement > those changes > we need to provide a new HBA driver which does not have the legacy > requirement > of mpt(7D). The proposed new driver mpt_sas(7D) will drive LSI MPT2 > compliant > SAS controllers which include LSI SAS200x/2108 series. > > 2) Proposal Summary > ------------------- > > The following features are supported by the proposed mpt_sas(7D) driver: > > 2.1) mpt_sas(7D) is DDI compliant and SCSA compliant as much as > applicable. > > 2.2) SAS initiator ports registration. > > 2.3) SAS/SATA/SMP target device dynamic enumeration / reconfiguration. > > 2.4) Target device representation conforms to FWARC 2008/013. > > 2.5) SAS/SATA devices multipathing support. > > 2.6) Power management, FMA and fast reboot support. > > 2.7) 3rd party ioctl support for management and firmware upgrade. > > > 3) Interface Table > ------------------- > > |----------------------------------------------------------| > | Interface Name | Classification | Comments | > |------------------|------------------+--------------------| > | mpt_sas(7D) | Committed | Driver name | > | | | | > | mpt_sas.conf | Committed | Configuration file | > | | | | > | SUNWmptsas | Committed | Package name | > | | | | > |----------------------------------------------------------| > > 4) Proposal Details > -------------------- > > 4.1) mpt_sas(7D) is as a SCSI/SAS HBA driver across SPARC and x86 > platforms > which supports stock SCSA interfaces. > > 4.2) The proposed driver supports multiple initiator ports. Exporting > the real > SCSI I-T nexus, once mpt_sas(7D) detects initiator ports, it > would register > the initiator ports. These are represented as individual child nexus > devinfo nodes in the Solaris device tree. All attached target > devices would > be children of a specific initiator port rather than PCI > function. The IR > (Integrated RAID) volumes are children of a special virtual > initiator port > nexus. > > 4.3) The driver class of proposed driver is "scsi-self-identifying" which > means that the driver is able to discover and enumerate target > devices > automatically rather than relying entries in the .conf file of > the target > driver. The proposed driver is able to discover and enumerate > SAS/SATA/SMP > /IR target devices. > > 4.4) The propsed driver represents attached target devices in standard > way which > would be compatible with future SCSA v3 naming rules. > > 4.4.1) The node names of the SAS/SATA target devices are generic node > names > and based on scsi device type (dtype). > > 4.4.2) The unit-address of SAS/SATA target devices are the form of > "target > identifier, lun". The detail specification of target identifier > please refer to FWARC 2008/013. The rule is generally of the form: > > 4.4.2.1) The target identifier of SAS target device is SAS address. > > 4.4.2.2) The target identifier of SATA target devices with ATA "Device > Name" > (108-111 words of ATA IDENTIFY) is the ATA "Device Name". > > 4.4.2.3) The target identifier of directly attached SATA device > without ATA > "Device Name" is attached PHY identifier. > > 4.4.2.4) The target identifier of indirectly attached SATA device > without ATA > "Device Name" is STP address which is assigned by expander. > > 4.4.3) The node name of SMP target is "smp". > > 4.4.4) The unit address of SMP target is SAS address. > > 4.4.5) The node name of IR volume is "disk". > > 4.4.6) The unit address of IR volume is form of "w$WWID,0". WWID of IR > volume > is World Wide Identifier of the IR volume by replacing the top > nibble > to "3". > > 4.5) The proposed driver supports Solaris IO Multipathing(MPxIO) for > SAS/SATA > devices and MPxIO is turned on by default. > Solaris I/O multipathing is enabled or disabled on SAS/SATA > devices which > associates to mpt_sas(7D) with the mpxio-disable property. > Specifying > mpxio-disable="no" activates I/O multipathing, while > mpxio-disable="yes" > disables the feature. I/O multipathing feature of mpt_sas(7D) may be > enabled or disabled on a per HBA basis. > > /kernel/drv/mpt_sas.conf will contain commentary about property > 'mpxio-disable', system administrators will need to modify the > property, > or use the stmsboot(1M) utility to disable or enable MPxIO. > > The default setting for 'mpxio-disable' (When missing the entry), > will be > "no". This means that the SAS/SATA MPxIO feature will be enabled > by default > unless specifically disabled by the system administrator. > > 4.6) The proposed driver supports Power management, FMA and fast > reboot as > required. > > 4.7) The proposed driver supports some Project Private ioctl > interfaces. These > enable the use of a vendor utility with the mpt_sas(7D) driver. > > 5) Packaging & Delivery: > > The mpt_sas(7d) driver will be delivered initially on both x86 and SPARC > architectures, the driver delivery will include: > > /kernel/drv/mpt_sas > /kernel/drv/mpt_sas.conf > /kernel/drv/amd64/mpt_sas > /kernel/drv/sparcv9/mpt_sas > > The mpt_sas(7d) manpage will be included in SUNWman. > > 6). Resources and Schedule: > > 6.1). Product Approval Committee requested information: > > 6.1.1) Consolidation or Component Name: ON > > 6.2) ARC review type: Fast Track > > 6.3) ARC Exposure: open > > 6) References > ------------- > > LSI MPI 2.0 revision J > PSARC/2006/703 MPxIO extension for Serial Attached SCSI (SAS) on mpt(7D) > PSARC/2007/595 Serial Attached SCSI (SAS) Management Protocol (SMP) > support > for Solaris > PSARC/2008/337 scsi-self-identifying > PSARC/2002/510 Sun Fire V440 (Chalupa) - Platform support [introduced > MPT] > PSARC/2005/097 Solaris support for LSI SAS1064 on Ontario > FWARC/2008/013 SCSI SAS 1275 Binding > > CR 6810441 Solaris needs to expose initiator port for multiple-port HBAs > CR 6762621 Add interconnect type for SAS transport. From Javen.Wu@sun.com Mon Apr 20 18:24:49 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3L1Onah003409 for ; Mon, 20 Apr 2009 18:24:49 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3L1OmZD023293 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Mon, 20 Apr 2009 18:24:48 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KIF00L01FXBXD00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 18:24:47 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIF006LNFXANW80@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 18:24:47 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3L1Ok3c023753 for ; Tue, 21 Apr 2009 01:24:46 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIF00000FSLSH00@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 21 Apr 2009 09:24:46 +0800 (SGT) Received: from [129.158.218.205] ([unknown] [129.158.218.205]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIF00JCTFX8M700@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 21 Apr 2009 09:24:46 +0800 (SGT) Date: Tue, 21 Apr 2009 01:19:54 +0000 From: Javen Wu Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49EC9205.3050607@sun.com> Sender: Javen.Wu@sun.com To: "Garrett D'Amore" Cc: Cecilia.Hu@sun.com, psarc-ext@sun.com, Yongfeng.Du@sun.com Message-id: <49ED1F3A.3060304@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <49EC9205.3050607@sun.com> User-Agent: Thunderbird 2.0.0.9 (X11/20080118) Status: RO Content-Length: 8694 Hi Garrett, Actually the proposed project includes the modification of stmsboot(1M) to support mpt_sas(7D), which is a utility to enable/disable mpxio for PHCI drivers . I assume all PHCI drivers should do the modification, I should have added a statement for stmsboot support in section 4.5. As for the utility to control individual instances of the driver is a good suggestion, we'll take it as a new project. :) thanks Javen Garrett D'Amore wrote: > +1. > > I'd like to encourage someone in the storage team to find a better > solution to configuring mpxio than the driver.conf properties. Anyone > who's worked with driver.conf tunables for PCI devices knows that > these are awkward and error prone, especially if you want to have > individual instances of the driver with different property settings. > (This problem is part of why Brussels exists for NIC drivers....) > Perhaps an SMF tunable or some other system similar to Brussels would > be more appropriate. > > - Garrett > > Cecilia Hu wrote: >> I am sponsoring this fast tack for Javen Wu and Dolpher Du. It is to >> provide a mpt_sas(7D) driver. Timer is set to 04/26, requested release >> binding is micro. >> >> -Cecilia >> >> >> >> >> -------------------------------------------------------------------- >> Name: Driver for LSI MPT2.0 compliant SAS 2.0 controller >> Submitters: Javen Wu, Dolpher Du >> >> 1) Background >> ------------- >> >> Over the past decade the storage industry has moved from traditional >> parallel >> SCSI based storage systems to more scalable serial storage >> connections. With >> the emergence of 3 and 6 Gigabit SAS, Sun and other vendors are >> revamping >> software storage stacks to support the new features. >> >> LSI's Fusion MPT Message Passing Technology forms the basis for a >> very popular >> family of Serial Attached SCSI HBAs. Sun makes extensive use of MPT for >> both PCI-E and PCI-X option cards as well as for motherboard hosted >> storage. >> The mpt(7D) driver was based on LSI's MPT v1.5, supporting both SAS and >> Parallel SCSI devices. >> >> LSI's support of the SAS 2.0 specification uses a new driver/firmware >> interface. >> MPT(rev2) is now under development. In order for Sun to implement >> those changes >> we need to provide a new HBA driver which does not have the legacy >> requirement >> of mpt(7D). The proposed new driver mpt_sas(7D) will drive LSI MPT2 >> compliant >> SAS controllers which include LSI SAS200x/2108 series. >> >> 2) Proposal Summary >> ------------------- >> >> The following features are supported by the proposed mpt_sas(7D) driver: >> >> 2.1) mpt_sas(7D) is DDI compliant and SCSA compliant as much as >> applicable. >> >> 2.2) SAS initiator ports registration. >> >> 2.3) SAS/SATA/SMP target device dynamic enumeration / reconfiguration. >> >> 2.4) Target device representation conforms to FWARC 2008/013. >> >> 2.5) SAS/SATA devices multipathing support. >> >> 2.6) Power management, FMA and fast reboot support. >> >> 2.7) 3rd party ioctl support for management and firmware upgrade. >> >> >> 3) Interface Table >> ------------------- >> >> |----------------------------------------------------------| >> | Interface Name | Classification | Comments | >> |------------------|------------------+--------------------| >> | mpt_sas(7D) | Committed | Driver name | >> | | | | >> | mpt_sas.conf | Committed | Configuration file | >> | | | | >> | SUNWmptsas | Committed | Package name | >> | | | | >> |----------------------------------------------------------| >> >> 4) Proposal Details >> -------------------- >> >> 4.1) mpt_sas(7D) is as a SCSI/SAS HBA driver across SPARC and x86 >> platforms >> which supports stock SCSA interfaces. >> >> 4.2) The proposed driver supports multiple initiator ports. Exporting >> the real >> SCSI I-T nexus, once mpt_sas(7D) detects initiator ports, it >> would register >> the initiator ports. These are represented as individual child >> nexus >> devinfo nodes in the Solaris device tree. All attached target >> devices would >> be children of a specific initiator port rather than PCI >> function. The IR >> (Integrated RAID) volumes are children of a special virtual >> initiator port >> nexus. >> >> 4.3) The driver class of proposed driver is "scsi-self-identifying" >> which >> means that the driver is able to discover and enumerate target >> devices >> automatically rather than relying entries in the .conf file of >> the target >> driver. The proposed driver is able to discover and enumerate >> SAS/SATA/SMP >> /IR target devices. >> >> 4.4) The propsed driver represents attached target devices in >> standard way which >> would be compatible with future SCSA v3 naming rules. >> >> 4.4.1) The node names of the SAS/SATA target devices are generic node >> names >> and based on scsi device type (dtype). >> >> 4.4.2) The unit-address of SAS/SATA target devices are the form of >> "target >> identifier, lun". The detail specification of target identifier >> please refer to FWARC 2008/013. The rule is generally of the >> form: >> >> 4.4.2.1) The target identifier of SAS target device is SAS address. >> >> 4.4.2.2) The target identifier of SATA target devices with ATA >> "Device Name" >> (108-111 words of ATA IDENTIFY) is the ATA "Device Name". >> >> 4.4.2.3) The target identifier of directly attached SATA device >> without ATA >> "Device Name" is attached PHY identifier. >> >> 4.4.2.4) The target identifier of indirectly attached SATA device >> without ATA >> "Device Name" is STP address which is assigned by expander. >> >> 4.4.3) The node name of SMP target is "smp". >> >> 4.4.4) The unit address of SMP target is SAS address. >> >> 4.4.5) The node name of IR volume is "disk". >> >> 4.4.6) The unit address of IR volume is form of "w$WWID,0". WWID of >> IR volume >> is World Wide Identifier of the IR volume by replacing the top >> nibble >> to "3". >> >> 4.5) The proposed driver supports Solaris IO Multipathing(MPxIO) for >> SAS/SATA >> devices and MPxIO is turned on by default. >> Solaris I/O multipathing is enabled or disabled on SAS/SATA >> devices which >> associates to mpt_sas(7D) with the mpxio-disable property. >> Specifying >> mpxio-disable="no" activates I/O multipathing, while >> mpxio-disable="yes" >> disables the feature. I/O multipathing feature of mpt_sas(7D) >> may be >> enabled or disabled on a per HBA basis. >> >> /kernel/drv/mpt_sas.conf will contain commentary about property >> 'mpxio-disable', system administrators will need to modify the >> property, >> or use the stmsboot(1M) utility to disable or enable MPxIO. >> >> The default setting for 'mpxio-disable' (When missing the >> entry), will be >> "no". This means that the SAS/SATA MPxIO feature will be enabled >> by default >> unless specifically disabled by the system administrator. >> >> 4.6) The proposed driver supports Power management, FMA and fast >> reboot as >> required. >> >> 4.7) The proposed driver supports some Project Private ioctl >> interfaces. These >> enable the use of a vendor utility with the mpt_sas(7D) driver. >> >> 5) Packaging & Delivery: >> >> The mpt_sas(7d) driver will be delivered initially on both x86 and SPARC >> architectures, the driver delivery will include: >> >> /kernel/drv/mpt_sas >> /kernel/drv/mpt_sas.conf >> /kernel/drv/amd64/mpt_sas >> /kernel/drv/sparcv9/mpt_sas >> >> The mpt_sas(7d) manpage will be included in SUNWman. >> >> 6). Resources and Schedule: >> >> 6.1). Product Approval Committee requested information: >> >> 6.1.1) Consolidation or Component Name: ON >> >> 6.2) ARC review type: Fast Track >> >> 6.3) ARC Exposure: open >> >> 6) References >> ------------- >> >> LSI MPI 2.0 revision J >> PSARC/2006/703 MPxIO extension for Serial Attached SCSI (SAS) on mpt(7D) >> PSARC/2007/595 Serial Attached SCSI (SAS) Management Protocol (SMP) >> support >> for Solaris >> PSARC/2008/337 scsi-self-identifying >> PSARC/2002/510 Sun Fire V440 (Chalupa) - Platform support [introduced >> MPT] >> PSARC/2005/097 Solaris support for LSI SAS1064 on Ontario >> FWARC/2008/013 SCSI SAS 1275 Binding >> >> CR 6810441 Solaris needs to expose initiator port for multiple-port HBAs >> CR 6762621 Add interconnect type for SAS transport. > From Torrey.McMahon@sun.com Mon Apr 20 19:10:00 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3L29x7l004868 for ; Mon, 20 Apr 2009 19:10:00 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3L29uDI005387 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 21 Apr 2009 03:09:58 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KIF00B01I0MP100@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 19:09:58 -0700 (PDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIF00453I0L7260@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 19:09:57 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3L29vox003608 for ; Tue, 21 Apr 2009 02:09:57 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIF00700HYY2M00@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 20:09:57 -0600 (MDT) Received: from [192.168.0.198] ([unknown] [69.143.10.149]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIF00KPNI0KFT30@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 20:09:57 -0600 (MDT) Date: Mon, 20 Apr 2009 22:09:58 -0400 From: Torrey McMahon Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49EC00CD.4020205@sun.com> Sender: Torrey.McMahon@sun.com To: Cecilia.Hu@sun.com Cc: psarc-ext@sun.com, Javen Wu , Yongfeng.Du@sun.com Message-id: <49ED2AF6.8020600@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090420 Lightning/1.0pre Shredder/3.0b3pre Status: RO Content-Length: 7649 Is mpt_sas going to replace mpt? Or could both drivers be loaded at the same time? If mpt_sas is going to support SAS and SATA drives isn't the name a a little confusing? On 4/20/2009 12:57 AM, Cecilia Hu wrote: > I am sponsoring this fast tack for Javen Wu and Dolpher Du. It is to > provide a mpt_sas(7D) driver. Timer is set to 04/26, requested release > binding is micro. > > -Cecilia > > > > > -------------------------------------------------------------------- > Name: Driver for LSI MPT2.0 compliant SAS 2.0 controller > Submitters: Javen Wu, Dolpher Du > > 1) Background > ------------- > > Over the past decade the storage industry has moved from traditional > parallel > SCSI based storage systems to more scalable serial storage > connections. With > the emergence of 3 and 6 Gigabit SAS, Sun and other vendors are revamping > software storage stacks to support the new features. > > LSI's Fusion MPT Message Passing Technology forms the basis for a very > popular > family of Serial Attached SCSI HBAs. Sun makes extensive use of MPT for > both PCI-E and PCI-X option cards as well as for motherboard hosted > storage. > The mpt(7D) driver was based on LSI's MPT v1.5, supporting both SAS and > Parallel SCSI devices. > > LSI's support of the SAS 2.0 specification uses a new driver/firmware > interface. > MPT(rev2) is now under development. In order for Sun to implement > those changes > we need to provide a new HBA driver which does not have the legacy > requirement > of mpt(7D). The proposed new driver mpt_sas(7D) will drive LSI MPT2 > compliant > SAS controllers which include LSI SAS200x/2108 series. > > 2) Proposal Summary > ------------------- > > The following features are supported by the proposed mpt_sas(7D) driver: > > 2.1) mpt_sas(7D) is DDI compliant and SCSA compliant as much as > applicable. > > 2.2) SAS initiator ports registration. > > 2.3) SAS/SATA/SMP target device dynamic enumeration / reconfiguration. > > 2.4) Target device representation conforms to FWARC 2008/013. > > 2.5) SAS/SATA devices multipathing support. > > 2.6) Power management, FMA and fast reboot support. > > 2.7) 3rd party ioctl support for management and firmware upgrade. > > > 3) Interface Table > ------------------- > > |----------------------------------------------------------| > | Interface Name | Classification | Comments | > |------------------|------------------+--------------------| > | mpt_sas(7D) | Committed | Driver name | > | | | | > | mpt_sas.conf | Committed | Configuration file | > | | | | > | SUNWmptsas | Committed | Package name | > | | | | > |----------------------------------------------------------| > > 4) Proposal Details > -------------------- > > 4.1) mpt_sas(7D) is as a SCSI/SAS HBA driver across SPARC and x86 > platforms > which supports stock SCSA interfaces. > > 4.2) The proposed driver supports multiple initiator ports. Exporting > the real > SCSI I-T nexus, once mpt_sas(7D) detects initiator ports, it > would register > the initiator ports. These are represented as individual child nexus > devinfo nodes in the Solaris device tree. All attached target > devices would > be children of a specific initiator port rather than PCI > function. The IR > (Integrated RAID) volumes are children of a special virtual > initiator port > nexus. > > 4.3) The driver class of proposed driver is "scsi-self-identifying" which > means that the driver is able to discover and enumerate target > devices > automatically rather than relying entries in the .conf file of > the target > driver. The proposed driver is able to discover and enumerate > SAS/SATA/SMP > /IR target devices. > > 4.4) The propsed driver represents attached target devices in standard > way which > would be compatible with future SCSA v3 naming rules. > > 4.4.1) The node names of the SAS/SATA target devices are generic node > names > and based on scsi device type (dtype). > > 4.4.2) The unit-address of SAS/SATA target devices are the form of > "target > identifier, lun". The detail specification of target identifier > please refer to FWARC 2008/013. The rule is generally of the form: > > 4.4.2.1) The target identifier of SAS target device is SAS address. > > 4.4.2.2) The target identifier of SATA target devices with ATA "Device > Name" > (108-111 words of ATA IDENTIFY) is the ATA "Device Name". > > 4.4.2.3) The target identifier of directly attached SATA device > without ATA > "Device Name" is attached PHY identifier. > > 4.4.2.4) The target identifier of indirectly attached SATA device > without ATA > "Device Name" is STP address which is assigned by expander. > > 4.4.3) The node name of SMP target is "smp". > > 4.4.4) The unit address of SMP target is SAS address. > > 4.4.5) The node name of IR volume is "disk". > > 4.4.6) The unit address of IR volume is form of "w$WWID,0". WWID of IR > volume > is World Wide Identifier of the IR volume by replacing the top > nibble > to "3". > > 4.5) The proposed driver supports Solaris IO Multipathing(MPxIO) for > SAS/SATA > devices and MPxIO is turned on by default. > Solaris I/O multipathing is enabled or disabled on SAS/SATA > devices which > associates to mpt_sas(7D) with the mpxio-disable property. > Specifying > mpxio-disable="no" activates I/O multipathing, while > mpxio-disable="yes" > disables the feature. I/O multipathing feature of mpt_sas(7D) may be > enabled or disabled on a per HBA basis. > > /kernel/drv/mpt_sas.conf will contain commentary about property > 'mpxio-disable', system administrators will need to modify the > property, > or use the stmsboot(1M) utility to disable or enable MPxIO. > > The default setting for 'mpxio-disable' (When missing the entry), > will be > "no". This means that the SAS/SATA MPxIO feature will be enabled > by default > unless specifically disabled by the system administrator. > > 4.6) The proposed driver supports Power management, FMA and fast > reboot as > required. > > 4.7) The proposed driver supports some Project Private ioctl > interfaces. These > enable the use of a vendor utility with the mpt_sas(7D) driver. > > 5) Packaging & Delivery: > > The mpt_sas(7d) driver will be delivered initially on both x86 and SPARC > architectures, the driver delivery will include: > > /kernel/drv/mpt_sas > /kernel/drv/mpt_sas.conf > /kernel/drv/amd64/mpt_sas > /kernel/drv/sparcv9/mpt_sas > > The mpt_sas(7d) manpage will be included in SUNWman. > > 6). Resources and Schedule: > > 6.1). Product Approval Committee requested information: > > 6.1.1) Consolidation or Component Name: ON > > 6.2) ARC review type: Fast Track > > 6.3) ARC Exposure: open > > 6) References > ------------- > > LSI MPI 2.0 revision J > PSARC/2006/703 MPxIO extension for Serial Attached SCSI (SAS) on mpt(7D) > PSARC/2007/595 Serial Attached SCSI (SAS) Management Protocol (SMP) > support > for Solaris > PSARC/2008/337 scsi-self-identifying > PSARC/2002/510 Sun Fire V440 (Chalupa) - Platform support [introduced > MPT] > PSARC/2005/097 Solaris support for LSI SAS1064 on Ontario > FWARC/2008/013 SCSI SAS 1275 Binding > > CR 6810441 Solaris needs to expose initiator port for multiple-port HBAs > CR 6762621 Add interconnect type for SAS transport. From James.McPherson@sun.com Mon Apr 20 19:16:13 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3L2GCJg004937 for ; Mon, 20 Apr 2009 19:16:12 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3L2G5u0010327 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 21 Apr 2009 10:16:11 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KIF00623IAY3U00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 19:16:10 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIF0060YIAXNHE0@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 19:16:10 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3L2G8vQ027163 for ; Tue, 21 Apr 2009 02:16:08 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIF00F00I80ON00@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 21 Apr 2009 10:16:08 +0800 (SGT) Received: from blinder ([unknown] [220.157.71.44]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIF00JESIATM720@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 21 Apr 2009 10:16:08 +0800 (SGT) Date: Tue, 21 Apr 2009 12:15:58 +1000 From: "James C. McPherson" Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49ED2AF6.8020600@sun.com> Sender: James.McPherson@sun.com To: Torrey McMahon Cc: Cecilia.Hu@sun.com, psarc-ext@sun.com, Yongfeng.Du@sun.com, Javen Wu Message-id: <20090421121558.000026d1@blinder> Organization: Sun Microsystems MIME-version: 1.0 X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.5; i386-pc-solaris2.11) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <49ED2AF6.8020600@sun.com> Status: RO Content-Length: 757 On Mon, 20 Apr 2009 22:09:58 -0400 Torrey McMahon wrote: > Is mpt_sas going to replace mpt? Or could both drivers be loaded at the > same time? Both drivers can be loaded at the same time. mpt(7d) supports Parallel SCSI and SAS generation 1 only. mpt_sas(7d) does not support Parallel SCSI or SAS generation 1. > If mpt_sas is going to support SAS and SATA drives isn't the name a a > little confusing? Perhaps. Since the driver is actually to support the HBA rather than SAS or SATA drives I don't think that matters. James -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog Kernel Conference Australia - http://au.sun.com/sunnews/events/2009/kernel From Javen.Wu@sun.com Mon Apr 20 19:30:50 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3L2Unt8005175 for ; Mon, 20 Apr 2009 19:30:50 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3L2Ujkk019922 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 21 Apr 2009 03:30:48 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KIF0080FIZA5600@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 19:30:46 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIF006VFIZ9NHE0@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 20 Apr 2009 19:30:46 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3L2Ujse028105 for ; Tue, 21 Apr 2009 02:30:45 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIF00200IU1DS00@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 21 Apr 2009 10:30:45 +0800 (SGT) Received: from [129.158.218.205] ([unknown] [129.158.218.205]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIF004PKIZ88I20@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 21 Apr 2009 10:30:45 +0800 (SGT) Date: Tue, 21 Apr 2009 02:25:54 +0000 From: Javen Wu Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49ED2AF6.8020600@sun.com> Sender: Javen.Wu@sun.com To: Torrey McMahon Cc: Cecilia.Hu@sun.com, psarc-ext@sun.com, Yongfeng.Du@sun.com Message-id: <49ED2EB2.6070609@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <49ED2AF6.8020600@sun.com> User-Agent: Thunderbird 2.0.0.9 (X11/20080118) Status: RO Content-Length: 8279 Hi Torrey, mpt_sas(7D) and mpt(7D) are different drivers to support different controllers. mpt(7D) is to support LSI parallel SCSI and SAS1.x controllers. mpt_sas(7D) is to support LSI SAS2.0 controllers. The naming mpt_sas(7D) is because the driver is to support SAS controllers regardless customer hook SAS or SATA drive to the controllers. Thanks Javen Torrey McMahon wrote: > Is mpt_sas going to replace mpt? Or could both drivers be loaded at > the same time? > > If mpt_sas is going to support SAS and SATA drives isn't the name a a > little confusing? > > > > On 4/20/2009 12:57 AM, Cecilia Hu wrote: >> I am sponsoring this fast tack for Javen Wu and Dolpher Du. It is to >> provide a mpt_sas(7D) driver. Timer is set to 04/26, requested release >> binding is micro. >> >> -Cecilia >> >> >> >> >> -------------------------------------------------------------------- >> Name: Driver for LSI MPT2.0 compliant SAS 2.0 controller >> Submitters: Javen Wu, Dolpher Du >> >> 1) Background >> ------------- >> >> Over the past decade the storage industry has moved from traditional >> parallel >> SCSI based storage systems to more scalable serial storage >> connections. With >> the emergence of 3 and 6 Gigabit SAS, Sun and other vendors are >> revamping >> software storage stacks to support the new features. >> >> LSI's Fusion MPT Message Passing Technology forms the basis for a >> very popular >> family of Serial Attached SCSI HBAs. Sun makes extensive use of MPT for >> both PCI-E and PCI-X option cards as well as for motherboard hosted >> storage. >> The mpt(7D) driver was based on LSI's MPT v1.5, supporting both SAS and >> Parallel SCSI devices. >> >> LSI's support of the SAS 2.0 specification uses a new driver/firmware >> interface. >> MPT(rev2) is now under development. In order for Sun to implement >> those changes >> we need to provide a new HBA driver which does not have the legacy >> requirement >> of mpt(7D). The proposed new driver mpt_sas(7D) will drive LSI MPT2 >> compliant >> SAS controllers which include LSI SAS200x/2108 series. >> >> 2) Proposal Summary >> ------------------- >> >> The following features are supported by the proposed mpt_sas(7D) driver: >> >> 2.1) mpt_sas(7D) is DDI compliant and SCSA compliant as much as >> applicable. >> >> 2.2) SAS initiator ports registration. >> >> 2.3) SAS/SATA/SMP target device dynamic enumeration / reconfiguration. >> >> 2.4) Target device representation conforms to FWARC 2008/013. >> >> 2.5) SAS/SATA devices multipathing support. >> >> 2.6) Power management, FMA and fast reboot support. >> >> 2.7) 3rd party ioctl support for management and firmware upgrade. >> >> >> 3) Interface Table >> ------------------- >> >> |----------------------------------------------------------| >> | Interface Name | Classification | Comments | >> |------------------|------------------+--------------------| >> | mpt_sas(7D) | Committed | Driver name | >> | | | | >> | mpt_sas.conf | Committed | Configuration file | >> | | | | >> | SUNWmptsas | Committed | Package name | >> | | | | >> |----------------------------------------------------------| >> >> 4) Proposal Details >> -------------------- >> >> 4.1) mpt_sas(7D) is as a SCSI/SAS HBA driver across SPARC and x86 >> platforms >> which supports stock SCSA interfaces. >> >> 4.2) The proposed driver supports multiple initiator ports. Exporting >> the real >> SCSI I-T nexus, once mpt_sas(7D) detects initiator ports, it >> would register >> the initiator ports. These are represented as individual child >> nexus >> devinfo nodes in the Solaris device tree. All attached target >> devices would >> be children of a specific initiator port rather than PCI >> function. The IR >> (Integrated RAID) volumes are children of a special virtual >> initiator port >> nexus. >> >> 4.3) The driver class of proposed driver is "scsi-self-identifying" >> which >> means that the driver is able to discover and enumerate target >> devices >> automatically rather than relying entries in the .conf file of >> the target >> driver. The proposed driver is able to discover and enumerate >> SAS/SATA/SMP >> /IR target devices. >> >> 4.4) The propsed driver represents attached target devices in >> standard way which >> would be compatible with future SCSA v3 naming rules. >> >> 4.4.1) The node names of the SAS/SATA target devices are generic node >> names >> and based on scsi device type (dtype). >> >> 4.4.2) The unit-address of SAS/SATA target devices are the form of >> "target >> identifier, lun". The detail specification of target identifier >> please refer to FWARC 2008/013. The rule is generally of the >> form: >> >> 4.4.2.1) The target identifier of SAS target device is SAS address. >> >> 4.4.2.2) The target identifier of SATA target devices with ATA >> "Device Name" >> (108-111 words of ATA IDENTIFY) is the ATA "Device Name". >> >> 4.4.2.3) The target identifier of directly attached SATA device >> without ATA >> "Device Name" is attached PHY identifier. >> >> 4.4.2.4) The target identifier of indirectly attached SATA device >> without ATA >> "Device Name" is STP address which is assigned by expander. >> >> 4.4.3) The node name of SMP target is "smp". >> >> 4.4.4) The unit address of SMP target is SAS address. >> >> 4.4.5) The node name of IR volume is "disk". >> >> 4.4.6) The unit address of IR volume is form of "w$WWID,0". WWID of >> IR volume >> is World Wide Identifier of the IR volume by replacing the top >> nibble >> to "3". >> >> 4.5) The proposed driver supports Solaris IO Multipathing(MPxIO) for >> SAS/SATA >> devices and MPxIO is turned on by default. >> Solaris I/O multipathing is enabled or disabled on SAS/SATA >> devices which >> associates to mpt_sas(7D) with the mpxio-disable property. >> Specifying >> mpxio-disable="no" activates I/O multipathing, while >> mpxio-disable="yes" >> disables the feature. I/O multipathing feature of mpt_sas(7D) >> may be >> enabled or disabled on a per HBA basis. >> >> /kernel/drv/mpt_sas.conf will contain commentary about property >> 'mpxio-disable', system administrators will need to modify the >> property, >> or use the stmsboot(1M) utility to disable or enable MPxIO. >> >> The default setting for 'mpxio-disable' (When missing the >> entry), will be >> "no". This means that the SAS/SATA MPxIO feature will be enabled >> by default >> unless specifically disabled by the system administrator. >> >> 4.6) The proposed driver supports Power management, FMA and fast >> reboot as >> required. >> >> 4.7) The proposed driver supports some Project Private ioctl >> interfaces. These >> enable the use of a vendor utility with the mpt_sas(7D) driver. >> >> 5) Packaging & Delivery: >> >> The mpt_sas(7d) driver will be delivered initially on both x86 and SPARC >> architectures, the driver delivery will include: >> >> /kernel/drv/mpt_sas >> /kernel/drv/mpt_sas.conf >> /kernel/drv/amd64/mpt_sas >> /kernel/drv/sparcv9/mpt_sas >> >> The mpt_sas(7d) manpage will be included in SUNWman. >> >> 6). Resources and Schedule: >> >> 6.1). Product Approval Committee requested information: >> >> 6.1.1) Consolidation or Component Name: ON >> >> 6.2) ARC review type: Fast Track >> >> 6.3) ARC Exposure: open >> >> 6) References >> ------------- >> >> LSI MPI 2.0 revision J >> PSARC/2006/703 MPxIO extension for Serial Attached SCSI (SAS) on mpt(7D) >> PSARC/2007/595 Serial Attached SCSI (SAS) Management Protocol (SMP) >> support >> for Solaris >> PSARC/2008/337 scsi-self-identifying >> PSARC/2002/510 Sun Fire V440 (Chalupa) - Platform support [introduced >> MPT] >> PSARC/2005/097 Solaris support for LSI SAS1064 on Ontario >> FWARC/2008/013 SCSI SAS 1275 Binding >> >> CR 6810441 Solaris needs to expose initiator port for multiple-port HBAs >> CR 6762621 Add interconnect type for SAS transport. From Torrey.McMahon@sun.com Wed Apr 22 12:37:09 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3MJb8X8020704 for ; Wed, 22 Apr 2009 12:37:08 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3MJb1ke060525 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 22 Apr 2009 13:37:08 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KII0020TP5V7500@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 22 Apr 2009 12:37:07 -0700 (PDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KII00AGVP5UXU90@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 22 Apr 2009 12:37:06 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3MJb6uD023184 for ; Wed, 22 Apr 2009 19:37:06 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KII00L00NK07T00@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 22 Apr 2009 13:37:06 -0600 (MDT) Received: from [192.168.0.198] ([unknown] [69.143.10.149]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KII0051VP4VKG20@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 22 Apr 2009 13:36:32 -0600 (MDT) Date: Wed, 22 Apr 2009 15:36:32 -0400 From: Torrey McMahon Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49ED2EB2.6070609@sun.com> Sender: Torrey.McMahon@sun.com To: Javen Wu Cc: Cecilia.Hu@sun.com, psarc-ext@sun.com, Yongfeng.Du@sun.com Message-id: <49EF71C0.2080200@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <49ED2AF6.8020600@sun.com> <49ED2EB2.6070609@sun.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090422 Lightning/1.0pre Shredder/3.0b3pre Status: RO Content-Length: 9184 It's really more of a nitpick. I just see some weird conversations like.... Customer: "I'm using this LSI SAS controller so I use mpt_sas, right?" Sun Tech: "No you use mpt." Customer: "Huh? What's the difference" Sun Tech: "mpt_sas is for new SAS controllers. mpt is for some of the older SAS controllers." Customer: "They both work on SAS controllers? How do I know which is which?" Sun Tech: "Man page[?]" Wouldn't something like mpt2 make more sense? Again, total nitpick. I'm not going to argue or anything over a name. It just seems kind of weird. :) On 4/20/2009 10:25 PM, Javen Wu wrote: > Hi Torrey, > mpt_sas(7D) and mpt(7D) are different drivers to support different > controllers. > mpt(7D) is to support LSI parallel SCSI and SAS1.x controllers. > mpt_sas(7D) is to support LSI SAS2.0 controllers. > The naming mpt_sas(7D) is because the driver is to support SAS > controllers regardless customer hook SAS or SATA drive to the > controllers. > > Thanks > Javen > > Torrey McMahon wrote: >> Is mpt_sas going to replace mpt? Or could both drivers be loaded at >> the same time? >> >> If mpt_sas is going to support SAS and SATA drives isn't the name a a >> little confusing? >> >> >> >> On 4/20/2009 12:57 AM, Cecilia Hu wrote: >>> I am sponsoring this fast tack for Javen Wu and Dolpher Du. It is to >>> provide a mpt_sas(7D) driver. Timer is set to 04/26, requested release >>> binding is micro. >>> >>> -Cecilia >>> >>> >>> >>> >>> -------------------------------------------------------------------- >>> Name: Driver for LSI MPT2.0 compliant SAS 2.0 controller >>> Submitters: Javen Wu, Dolpher Du >>> >>> 1) Background >>> ------------- >>> >>> Over the past decade the storage industry has moved from traditional >>> parallel >>> SCSI based storage systems to more scalable serial storage >>> connections. With >>> the emergence of 3 and 6 Gigabit SAS, Sun and other vendors are >>> revamping >>> software storage stacks to support the new features. >>> >>> LSI's Fusion MPT Message Passing Technology forms the basis for a >>> very popular >>> family of Serial Attached SCSI HBAs. Sun makes extensive use of MPT for >>> both PCI-E and PCI-X option cards as well as for motherboard hosted >>> storage. >>> The mpt(7D) driver was based on LSI's MPT v1.5, supporting both SAS and >>> Parallel SCSI devices. >>> >>> LSI's support of the SAS 2.0 specification uses a new >>> driver/firmware interface. >>> MPT(rev2) is now under development. In order for Sun to implement >>> those changes >>> we need to provide a new HBA driver which does not have the legacy >>> requirement >>> of mpt(7D). The proposed new driver mpt_sas(7D) will drive LSI MPT2 >>> compliant >>> SAS controllers which include LSI SAS200x/2108 series. >>> >>> 2) Proposal Summary >>> ------------------- >>> >>> The following features are supported by the proposed mpt_sas(7D) >>> driver: >>> >>> 2.1) mpt_sas(7D) is DDI compliant and SCSA compliant as much as >>> applicable. >>> >>> 2.2) SAS initiator ports registration. >>> >>> 2.3) SAS/SATA/SMP target device dynamic enumeration / reconfiguration. >>> >>> 2.4) Target device representation conforms to FWARC 2008/013. >>> >>> 2.5) SAS/SATA devices multipathing support. >>> >>> 2.6) Power management, FMA and fast reboot support. >>> >>> 2.7) 3rd party ioctl support for management and firmware upgrade. >>> >>> >>> 3) Interface Table >>> ------------------- >>> >>> |----------------------------------------------------------| >>> | Interface Name | Classification | Comments | >>> |------------------|------------------+--------------------| >>> | mpt_sas(7D) | Committed | Driver name | >>> | | | | >>> | mpt_sas.conf | Committed | Configuration file | >>> | | | | >>> | SUNWmptsas | Committed | Package name | >>> | | | | >>> |----------------------------------------------------------| >>> >>> 4) Proposal Details >>> -------------------- >>> >>> 4.1) mpt_sas(7D) is as a SCSI/SAS HBA driver across SPARC and x86 >>> platforms >>> which supports stock SCSA interfaces. >>> >>> 4.2) The proposed driver supports multiple initiator ports. >>> Exporting the real >>> SCSI I-T nexus, once mpt_sas(7D) detects initiator ports, it >>> would register >>> the initiator ports. These are represented as individual child >>> nexus >>> devinfo nodes in the Solaris device tree. All attached target >>> devices would >>> be children of a specific initiator port rather than PCI >>> function. The IR >>> (Integrated RAID) volumes are children of a special virtual >>> initiator port >>> nexus. >>> >>> 4.3) The driver class of proposed driver is "scsi-self-identifying" >>> which >>> means that the driver is able to discover and enumerate target >>> devices >>> automatically rather than relying entries in the .conf file of >>> the target >>> driver. The proposed driver is able to discover and enumerate >>> SAS/SATA/SMP >>> /IR target devices. >>> >>> 4.4) The propsed driver represents attached target devices in >>> standard way which >>> would be compatible with future SCSA v3 naming rules. >>> >>> 4.4.1) The node names of the SAS/SATA target devices are generic >>> node names >>> and based on scsi device type (dtype). >>> >>> 4.4.2) The unit-address of SAS/SATA target devices are the form of >>> "target >>> identifier, lun". The detail specification of target identifier >>> please refer to FWARC 2008/013. The rule is generally of the >>> form: >>> >>> 4.4.2.1) The target identifier of SAS target device is SAS address. >>> >>> 4.4.2.2) The target identifier of SATA target devices with ATA >>> "Device Name" >>> (108-111 words of ATA IDENTIFY) is the ATA "Device Name". >>> >>> 4.4.2.3) The target identifier of directly attached SATA device >>> without ATA >>> "Device Name" is attached PHY identifier. >>> >>> 4.4.2.4) The target identifier of indirectly attached SATA device >>> without ATA >>> "Device Name" is STP address which is assigned by expander. >>> >>> 4.4.3) The node name of SMP target is "smp". >>> >>> 4.4.4) The unit address of SMP target is SAS address. >>> >>> 4.4.5) The node name of IR volume is "disk". >>> >>> 4.4.6) The unit address of IR volume is form of "w$WWID,0". WWID of >>> IR volume >>> is World Wide Identifier of the IR volume by replacing the >>> top nibble >>> to "3". >>> >>> 4.5) The proposed driver supports Solaris IO Multipathing(MPxIO) for >>> SAS/SATA >>> devices and MPxIO is turned on by default. >>> Solaris I/O multipathing is enabled or disabled on SAS/SATA >>> devices which >>> associates to mpt_sas(7D) with the mpxio-disable property. >>> Specifying >>> mpxio-disable="no" activates I/O multipathing, while >>> mpxio-disable="yes" >>> disables the feature. I/O multipathing feature of mpt_sas(7D) >>> may be >>> enabled or disabled on a per HBA basis. >>> >>> /kernel/drv/mpt_sas.conf will contain commentary about property >>> 'mpxio-disable', system administrators will need to modify the >>> property, >>> or use the stmsboot(1M) utility to disable or enable MPxIO. >>> >>> The default setting for 'mpxio-disable' (When missing the >>> entry), will be >>> "no". This means that the SAS/SATA MPxIO feature will be >>> enabled by default >>> unless specifically disabled by the system administrator. >>> >>> 4.6) The proposed driver supports Power management, FMA and fast >>> reboot as >>> required. >>> >>> 4.7) The proposed driver supports some Project Private ioctl >>> interfaces. These >>> enable the use of a vendor utility with the mpt_sas(7D) driver. >>> >>> 5) Packaging & Delivery: >>> >>> The mpt_sas(7d) driver will be delivered initially on both x86 and >>> SPARC >>> architectures, the driver delivery will include: >>> >>> /kernel/drv/mpt_sas >>> /kernel/drv/mpt_sas.conf >>> /kernel/drv/amd64/mpt_sas >>> /kernel/drv/sparcv9/mpt_sas >>> >>> The mpt_sas(7d) manpage will be included in SUNWman. >>> >>> 6). Resources and Schedule: >>> >>> 6.1). Product Approval Committee requested information: >>> >>> 6.1.1) Consolidation or Component Name: ON >>> >>> 6.2) ARC review type: Fast Track >>> >>> 6.3) ARC Exposure: open >>> >>> 6) References >>> ------------- >>> >>> LSI MPI 2.0 revision J >>> PSARC/2006/703 MPxIO extension for Serial Attached SCSI (SAS) on >>> mpt(7D) >>> PSARC/2007/595 Serial Attached SCSI (SAS) Management Protocol (SMP) >>> support >>> for Solaris >>> PSARC/2008/337 scsi-self-identifying >>> PSARC/2002/510 Sun Fire V440 (Chalupa) - Platform support >>> [introduced MPT] >>> PSARC/2005/097 Solaris support for LSI SAS1064 on Ontario >>> FWARC/2008/013 SCSI SAS 1275 Binding >>> >>> CR 6810441 Solaris needs to expose initiator port for multiple-port >>> HBAs >>> CR 6762621 Add interconnect type for SAS transport. > From James.McPherson@sun.com Wed Apr 22 17:21:54 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3N0Lrsn023725 for ; Wed, 22 Apr 2009 17:21:53 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3N0LnTS022083 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Thu, 23 Apr 2009 08:21:52 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KIJ00G092CD2Q00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 22 Apr 2009 17:21:49 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIJ00BMY2CCXBD0@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 22 Apr 2009 17:21:49 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3N0Lm1D018005 for ; Thu, 23 Apr 2009 00:21:48 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIJ0060028QJT00@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu, 23 Apr 2009 08:21:48 +0800 (SGT) Received: from blinder ([unknown] [220.157.71.44]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIJ00D7R2C92980@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu, 23 Apr 2009 08:21:48 +0800 (SGT) Date: Thu, 23 Apr 2009 10:11:58 +1000 From: "James C. McPherson" Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49EF71C0.2080200@sun.com> Sender: James.McPherson@sun.com To: Torrey McMahon Cc: Javen Wu , Cecilia.Hu@sun.com, psarc-ext@sun.com, Yongfeng.Du@sun.com Message-id: <20090423101158.00005079@blinder> Organization: Sun Microsystems MIME-version: 1.0 X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.5; i386-pc-solaris2.11) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <49ED2AF6.8020600@sun.com> <49ED2EB2.6070609@sun.com> <49EF71C0.2080200@sun.com> Status: RO Content-Length: 1605 On Wed, 22 Apr 2009 15:36:32 -0400 Torrey McMahon wrote: > It's really more of a nitpick. I just see some weird conversations like.... > > Customer: "I'm using this LSI SAS controller so I use mpt_sas, right?" > Sun Tech: "No you use mpt." > Customer: "Huh? What's the difference" > Sun Tech: "mpt_sas is for new SAS controllers. mpt is for some of > the older SAS controllers." > Customer: "They both work on SAS controllers? How do I know which is > which?" > Sun Tech: "Man page[?]" > > Wouldn't something like mpt2 make more sense? Again, total nitpick. I'm > not going to argue or anything over a name. It just seems kind of weird. :) mpt2 is a driver + instance number, which would interfere with existing installations. What we're trying to do with this mpt_sas name (and the mr_sas name for the MegaRAID SAS 2nd gen HBAs) is make it clear that this is a driver for a closely related family of hardware. The chips which the customer will most likely get to know that use this new driver are all LSI SAS2..., whereas for mpt(7d) they are LSI SAS1.... and the parallel SCSI forms. So your conversation snippet above should say > Sun Tech: "mpt_sas is for 2nd generation LSI SAS controllers. > mpt is for the 1st generation LSI SAS controllers." And yes, the manpages will make this very clear. James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog Kernel Conference Australia - http://au.sun.com/sunnews/events/2009/kernel From Cecilia.Hu@sun.com Tue Apr 28 00:39:06 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3S7d57W029559 for ; Tue, 28 Apr 2009 00:39:06 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3S7cwA7029344 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 28 Apr 2009 15:39:04 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KIS0040RVX28900@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 28 Apr 2009 01:39:02 -0600 (MDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIS000VSVX10R30@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 28 Apr 2009 01:39:02 -0600 (MDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3S7d0C9007125 for ; Tue, 28 Apr 2009 07:39:01 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIS00H00VM3DG00@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 28 Apr 2009 15:39:00 +0800 (SGT) Received: from [129.158.218.98] ([unknown] [129.158.218.98]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIS00FJYVWZBSG0@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 28 Apr 2009 15:39:00 +0800 (SGT) Date: Tue, 28 Apr 2009 15:36:23 +0800 From: Cecilia Hu Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <20090423101158.00005079@blinder> Sender: Cecilia.Hu@sun.com To: "James C. McPherson" Cc: Torrey McMahon , Javen Wu , psarc-ext@sun.com, Yongfeng.Du@sun.com Reply-to: Cecilia.Hu@sun.com Message-id: <49F6B1F7.4050005@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <49ED2AF6.8020600@sun.com> <49ED2EB2.6070609@sun.com> <49EF71C0.2080200@sun.com> <20090423101158.00005079@blinder> User-Agent: Thunderbird 2.0.0.9 (X11/20080128) Status: RO Content-Length: 179 This case has got enough supports and all questions were addressed. Timer was also expired at 04/26/2009. If no more comments, this case is "closed approved". Thanks, -Cecilia From Cecilia.Hu@sun.com Wed Apr 29 19:53:24 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3U2rNg1012260 for ; Wed, 29 Apr 2009 19:53:23 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3U2rIcA021679; Thu, 30 Apr 2009 03:53:22 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KIW00F0D80VSE00@nwk-avmta-2.sfbay.sun.com>; Wed, 29 Apr 2009 19:53:19 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIW00F8N80UPR00@nwk-avmta-2.sfbay.sun.com>; Wed, 29 Apr 2009 19:53:19 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3U2rHb2001282; Thu, 30 Apr 2009 02:53:17 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIW00D007YXO700@mail-apac.sun.com>; Thu, 30 Apr 2009 10:53:17 +0800 (SGT) Received: from [129.158.218.98] ([unknown] [129.158.218.98]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIW001P980SZ560@mail-apac.sun.com>; Thu, 30 Apr 2009 10:53:17 +0800 (SGT) Date: Thu, 30 Apr 2009 10:50:40 +0800 From: Cecilia Hu Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49F6B1F7.4050005@sun.com> Sender: Cecilia.Hu@sun.com To: psarc-ext@sun.com Cc: Yongfeng.Du@sun.com Reply-to: Cecilia.Hu@sun.com Message-id: <49F91200.8020008@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <49ED2AF6.8020600@sun.com> <49ED2EB2.6070609@sun.com> <49EF71C0.2080200@sun.com> <20090423101158.00005079@blinder> <49F6B1F7.4050005@sun.com> User-Agent: Thunderbird 2.0.0.9 (X11/20080128) Status: RO Content-Length: 53 This case was approved at today's meeting. -Cecilia From ceri@submonkey.net Sat May 9 06:31:16 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n49DVG5t021667 for ; Sat, 9 May 2009 06:31:16 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n49DVCP0012177; Sat, 9 May 2009 06:31:12 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KJD00401PK0WO00@nwk-avmta-2.sfbay.sun.com>; Sat, 09 May 2009 06:31:12 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJD00MXLPJZLD30@nwk-avmta-2.sfbay.sun.com>; Sat, 09 May 2009 06:31:12 -0700 (PDT) Received: from relay41i.sun.com ([192.5.209.70]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n49D93HU003878; Sat, 09 May 2009 13:31:11 +0000 (GMT) Received: from mmp43es.mmp.us.syntegra.com ([160.41.221.12] [160.41.221.12]) by relay41i.sun.com with ESMTP id BT-MMP-3164382; Sat, 09 May 2009 13:31:11 +0000 (Z) Received: from relay44i.sun.com (relay44i.sun.com [192.5.209.118]) by mmp43es.mmp.us.syntegra.com with ESMTP id BT-MMP-4108188; Sat, 09 May 2009 13:31:09 +0000 (Z) Received: from scuttle.submonkey.net ([208.111.43.184] [208.111.43.184]) by relay4i.sun.com with ESMTP id BT-MMP-1574948; Sat, 09 May 2009 13:31:08 +0000 (Z) Received: from cpc1-cdif1-0-0-cust63.cdif.cable.ntl.com ([81.104.164.64] helo=shrike.submonkey.net) by scuttle.submonkey.net with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M2mdw-000540-4k; Sat, 09 May 2009 13:31:08 +0000 Received: from ceri by shrike.submonkey.net with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1M2mdu-000K4Z-08; Sat, 09 May 2009 14:31:06 +0100 Date: Sat, 09 May 2009 14:31:05 +0100 From: Ceri Davies Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49ED1F3A.3060304@sun.com> Sender: Ceri Davies To: Javen Wu Cc: "Garrett D'Amore" , Cecilia.Hu@sun.com, psarc-ext@sun.com, Yongfeng.Du@sun.com Message-id: <20090509133105.GA87080@submonkey.net> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=FCuugMFkClbJLl1L Content-disposition: inline X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-PGP: finger ceri@FreeBSD.org X-Antispam: No, score=0.0/5.0, scanned in 1.133sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <49EC00CD.4020205@sun.com> <49EC9205.3050607@sun.com> <49ED1F3A.3060304@sun.com> User-Agent: Mutt/1.5.18 (2008-05-17) Status: RO Content-Length: 1235 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 21, 2009 at 01:19:54AM +0000, Javen Wu wrote: > Hi Garrett, >=20 > Actually the proposed project includes the modification of stmsboot(1M)= =20 > to support mpt_sas(7D), which is a utility to enable/disable mpxio for=20 > PHCI drivers . I assume all PHCI drivers should do the modification, I=20 > should have added a statement for stmsboot support in section 4.5. > As for the utility to control individual instances of the driver is a=20 > good suggestion, we'll take it as a new project. :) As someone who just migrated data from one SAN where mpxio was not in use to a different SAN where it was, some way of doing it without rebooting would be nice too. Ceri --=20 That must be wonderful! I don't understand it at all. -- Moliere --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFKBYWZocfcwTS3JF8RAhItAJ49ut90Da6ro0t8A8apPX/d5EGzkQCfYpEo eaj+MBq15aPg4pWvFbp1b14= =rUod -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From James.McPherson@sun.com Sun May 10 03:54:39 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n4AAsbka017599 for ; Sun, 10 May 2009 03:54:38 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n4AAsavI013119 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Sun, 10 May 2009 18:54:37 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KJF0040JCYZEG00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Sun, 10 May 2009 04:54:35 -0600 (MDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJF008LICYTDQ60@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Sun, 10 May 2009 04:54:35 -0600 (MDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n4AAsTpu000507 for ; Sun, 10 May 2009 10:54:29 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KJF00J00CJOYX00@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Sun, 10 May 2009 18:54:28 +0800 (SGT) Received: from blinder ([unknown] [220.157.71.44]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KJF00LR7CYQMU20@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Sun, 10 May 2009 18:54:28 +0800 (SGT) Date: Sun, 10 May 2009 20:54:22 +1000 From: "James C. McPherson" Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <20090509133105.GA87080@submonkey.net> Sender: James.McPherson@sun.com To: Ceri Davies Cc: Javen Wu , "Garrett D'Amore" , Cecilia.Hu@sun.com, psarc-ext@sun.com, Yongfeng.Du@sun.com Message-id: <20090510205422.0000172c@blinder> Organization: Sun Microsystems MIME-version: 1.0 X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.5; i386-pc-solaris2.11) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <49EC9205.3050607@sun.com> <49ED1F3A.3060304@sun.com> <20090509133105.GA87080@submonkey.net> Status: RO Content-Length: 1067 On Sat, 09 May 2009 14:31:05 +0100 Ceri Davies wrote: > On Tue, Apr 21, 2009 at 01:19:54AM +0000, Javen Wu wrote: > > Hi Garrett, > > > > Actually the proposed project includes the modification of stmsboot(1M) > > to support mpt_sas(7D), which is a utility to enable/disable mpxio for > > PHCI drivers . I assume all PHCI drivers should do the modification, I > > should have added a statement for stmsboot support in section 4.5. > > As for the utility to control individual instances of the driver is a > > good suggestion, we'll take it as a new project. :) > > As someone who just migrated data from one SAN where mpxio was not in > use to a different SAN where it was, some way of doing it without > rebooting would be nice too. That *should* be orthogonal to the problem of data migration, let alone to this case. James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog Kernel Conference Australia - http://au.sun.com/sunnews/events/2009/kernel From Frank.Che@sun.com Mon Jul 6 19:23:31 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n672NUra024305 for ; Mon, 6 Jul 2009 19:23:30 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n672NR54002683 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 7 Jul 2009 10:23:29 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KME001033Z3EP00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 06 Jul 2009 19:23:27 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KME000OJ3Z2AI60@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 06 Jul 2009 19:23:27 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n672NQgh003611 for ; Tue, 07 Jul 2009 02:23:26 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KME00C003VUFO00@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 10:23:25 +0800 (SGT) Received: from [129.158.218.60] ([unknown] [129.158.218.60]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KME007IN3YU4Y10@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 10:23:25 +0800 (SGT) Date: Tue, 07 Jul 2009 10:19:33 +0800 From: Frank Che Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <49EC00CD.4020205@sun.com> Sender: Frank.Che@sun.com To: psarc-ext@sun.com Cc: Javen Wu , Yongfeng.Du@sun.com Message-id: <4A52B0B5.4080801@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> User-Agent: Thunderbird 2.0.0.19 (X11/20090218) Status: RO Content-Length: 504 The project team would like to change the release binding of this project from micro to patch, for back-porting purpose. If there is any concern on this, please let the project team know. I think this change is qualified for self review. If there is concern, I can upgrade it to a fast track. Frank. Cecilia Hu wrote: > I am sponsoring this fast tack for Javen Wu and Dolpher Du. It is to > provide a mpt_sas(7D) driver. Timer is set to 04/26, requested release > binding is micro. > > -Cecilia > From gdamore@sun.com Mon Jul 6 21:15:49 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n674FnMa027577 for ; Mon, 6 Jul 2009 21:15:49 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n674FmkV023969 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Mon, 6 Jul 2009 22:15:49 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KME00C0396C4000@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 06 Jul 2009 22:15:48 -0600 (MDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KME00AD896BN920@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 06 Jul 2009 22:15:47 -0600 (MDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n674FlM1003929 for ; Mon, 06 Jul 2009 21:15:47 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KME003008UP4H00@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 06 Jul 2009 21:15:47 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KME00M5W96BSJ30@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 06 Jul 2009 21:15:47 -0700 (PDT) Date: Mon, 06 Jul 2009 21:15:46 -0700 From: "Garrett D'Amore" Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <4A52B0B5.4080801@sun.com> Sender: Garrett.Damore@sun.com To: Frank Che Cc: psarc-ext@sun.com, Javen Wu , Yongfeng.Du@sun.com Message-id: <4A52CBF2.7040101@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <4A52B0B5.4080801@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 915 Frank Che wrote: > The project team would like to change the release binding of this > project from micro to patch, for back-porting purpose. If there is any > concern on this, please let the project team know. > > I think this change is qualified for self review. If there is concern, > I can upgrade it to a fast track. I think since you requested micro binding originally, this is trivially obvious. Indeed, I think many people these days treat micro binding as synonymous with patch binding. (We haven't had a "micro" release since Solaris 2.5.1.) For C-Team's point of view, I think you can just go ahead and proceed as if you originally requested patch binding. - Garrett > > Frank. > > Cecilia Hu wrote: >> I am sponsoring this fast tack for Javen Wu and Dolpher Du. It is to >> provide a mpt_sas(7D) driver. Timer is set to 04/26, requested release >> binding is micro. >> >> -Cecilia >> From Darren.Moffat@Sun.COM Tue Jul 7 01:59:58 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n678xwmh003327 for ; Tue, 7 Jul 2009 01:59:58 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n678xw8v010957 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 7 Jul 2009 01:59:58 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KME00D01MBYN100@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 01:59:58 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KME00L65MBXUUF0@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 01:59:58 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n678xvWr001371 for ; Tue, 07 Jul 2009 08:59:57 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KME00600K0A2B00@fe-emea-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 09:59:57 +0100 (BST) Received: from [129.156.173.199] ([unknown] [129.156.173.199]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KME00NLVMB32500@fe-emea-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 09:59:28 +0100 (BST) Date: Tue, 07 Jul 2009 09:59:27 +0100 From: Darren J Moffat Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <4A52CBF2.7040101@sun.com> Sender: Darren.Moffat@Sun.COM To: "Garrett D'Amore" Cc: Frank Che , psarc-ext@Sun.COM, Yongfeng.Du@Sun.COM, Javen Wu Message-id: <4A530E6F.8060101@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <4A52B0B5.4080801@sun.com> <4A52CBF2.7040101@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20090127) Status: RO Content-Length: 1432 Garrett D'Amore wrote: > Frank Che wrote: >> The project team would like to change the release binding of this >> project from micro to patch, for back-porting purpose. If there is any >> concern on this, please let the project team know. >> >> I think this change is qualified for self review. If there is concern, >> I can upgrade it to a fast track. > > I think since you requested micro binding originally, this is trivially > obvious. Indeed, I think many people these days treat micro binding as > synonymous with patch binding. (We haven't had a "micro" release since > Solaris 2.5.1.) > > For C-Team's point of view, I think you can just go ahead and proceed as > if you originally requested patch binding. There is a very important difference between micro and patch though and that is the delivery mechanism. A micro release can be assumed to be fresh installer or upgraded to but a patch release could need the feature applied by 'patchadd' as well as being upgraded to in a fresh bitted release. This case introduces a new package (SUNWmptsas) so as long as that can be properly dealt with in the patch release train I have no problem with the change of binding. Also for drivers in particular the difference between micro and patch can be important if the device is needed as a boot device (which I assume would be the case for some hardware with the driver form this case). -- Darren J Moffat From gdamore@sun.com Tue Jul 7 08:57:09 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n67Fv9ja016390 for ; Tue, 7 Jul 2009 08:57:09 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n67Fv2wk016225 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 7 Jul 2009 08:57:09 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KMF00H0X5N8SL00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 09:57:08 -0600 (MDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KMF009RR5N6LR70@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 09:57:06 -0600 (MDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n67Fv6LA006785 for ; Tue, 07 Jul 2009 08:57:06 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KMF001005GZM000@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 08:57:06 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KMF009695N1VUL0@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 08:57:01 -0700 (PDT) Date: Tue, 07 Jul 2009 08:57:01 -0700 From: "Garrett D'Amore" Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <4A530E6F.8060101@Sun.COM> Sender: Garrett.Damore@sun.com To: Darren J Moffat Cc: Frank Che , psarc-ext@sun.com, Yongfeng.Du@sun.com, Javen Wu Message-id: <4A53704D.2090906@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <4A52B0B5.4080801@sun.com> <4A52CBF2.7040101@sun.com> <4A530E6F.8060101@Sun.COM> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 1786 Darren J Moffat wrote: > Garrett D'Amore wrote: >> Frank Che wrote: >>> The project team would like to change the release binding of this >>> project from micro to patch, for back-porting purpose. If there is >>> any concern on this, please let the project team know. >>> >>> I think this change is qualified for self review. If there is >>> concern, I can upgrade it to a fast track. >> >> I think since you requested micro binding originally, this is >> trivially obvious. Indeed, I think many people these days treat >> micro binding as synonymous with patch binding. (We haven't had a >> "micro" release since Solaris 2.5.1.) >> >> For C-Team's point of view, I think you can just go ahead and proceed >> as if you originally requested patch binding. > > There is a very important difference between micro and patch though > and that is the delivery mechanism. A micro release can be assumed to > be fresh installer or upgraded to but a patch release could need the > feature applied by 'patchadd' as well as being upgraded to in a fresh > bitted release. This case introduces a new package (SUNWmptsas) so as > long as that can be properly dealt with in the patch release train I > have no problem with the change of binding. > C-Team is apparently confused... while the driver is intended for the feature-patch gate (i.e. for delivery as part of a Solaris 10 update), they have made a point of requesting the project go back and ask for patch binding. > Also for drivers in particular the difference between micro and patch > can be important if the device is needed as a boot device (which I > assume would be the case for some hardware with the driver form this > case). > I'm not sure that the distinction matters that much in practice. - Garrett From Darren.Moffat@sun.com Tue Jul 7 09:04:13 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n67G4CkH016530 for ; Tue, 7 Jul 2009 09:04:13 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n67G48g1011989 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 7 Jul 2009 17:04:12 +0100 (BST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KMF00I6T5YZF700@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 10:04:11 -0600 (MDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KMF009P95YVLH90@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 10:04:07 -0600 (MDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n67G468D016617 for ; Tue, 07 Jul 2009 16:04:06 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KMF00B005RFAL00@fe-emea-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 17:04:06 +0100 (BST) Received: from [129.156.173.199] ([unknown] [129.156.173.199]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KMF0006S5YF9T80@fe-emea-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 17:03:53 +0100 (BST) Date: Tue, 07 Jul 2009 17:03:51 +0100 From: Darren J Moffat Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <4A53704D.2090906@sun.com> Sender: Darren.Moffat@sun.com To: "Garrett D'Amore" Cc: Frank Che , psarc-ext@sun.com, Yongfeng.Du@sun.com, Javen Wu Message-id: <4A5371E7.2060402@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <4A52B0B5.4080801@sun.com> <4A52CBF2.7040101@sun.com> <4A530E6F.8060101@Sun.COM> <4A53704D.2090906@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20090127) Status: RO Content-Length: 2194 Garrett D'Amore wrote: > Darren J Moffat wrote: >> Garrett D'Amore wrote: >>> Frank Che wrote: >>>> The project team would like to change the release binding of this >>>> project from micro to patch, for back-porting purpose. If there is >>>> any concern on this, please let the project team know. >>>> >>>> I think this change is qualified for self review. If there is >>>> concern, I can upgrade it to a fast track. >>> >>> I think since you requested micro binding originally, this is >>> trivially obvious. Indeed, I think many people these days treat >>> micro binding as synonymous with patch binding. (We haven't had a >>> "micro" release since Solaris 2.5.1.) >>> >>> For C-Team's point of view, I think you can just go ahead and proceed >>> as if you originally requested patch binding. >> >> There is a very important difference between micro and patch though >> and that is the delivery mechanism. A micro release can be assumed to >> be fresh installer or upgraded to but a patch release could need the >> feature applied by 'patchadd' as well as being upgraded to in a fresh >> bitted release. This case introduces a new package (SUNWmptsas) so as >> long as that can be properly dealt with in the patch release train I >> have no problem with the change of binding. >> > > C-Team is apparently confused... while the driver is intended for the > feature-patch gate (i.e. for delivery as part of a Solaris 10 update), > they have made a point of requesting the project go back and ask for > patch binding. I don't think the C-Team is confused. Solaris 10 updates are not micro releases they are patch binding releases. >> Also for drivers in particular the difference between micro and patch >> can be important if the device is needed as a boot device (which I >> assume would be the case for some hardware with the driver form this >> case). >> > I'm not sure that the distinction matters that much in practice. In general it doesn't but there are cases were it does, in particular some times it is difficult to patch something into existence or worse once in hard to get out (upgrade is one way but patches can be backed out). -- Darren J Moffat From gdamore@sun.com Tue Jul 7 09:10:45 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n67GAjxO016775 for ; Tue, 7 Jul 2009 09:10:45 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n67GAeg4020277 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 7 Jul 2009 09:10:45 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KMF0012369RC700@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 09:10:39 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KMF00CG169P9M60@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 09:10:37 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n67GAbQ8025300 for ; Tue, 07 Jul 2009 09:10:37 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KMF001005GZM000@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 09:10:37 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KMF009ZP69J5JC0@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 09:10:31 -0700 (PDT) Date: Tue, 07 Jul 2009 09:10:31 -0700 From: "Garrett D'Amore" Subject: Re: PSARC 2008/443 Driver for LSI MPT2.0 compliant SAS 2.0 controller In-reply-to: <4A5371E7.2060402@Sun.COM> Sender: Garrett.Damore@sun.com To: Darren J Moffat Cc: Frank Che , psarc-ext@sun.com, Yongfeng.Du@sun.com, Javen Wu Message-id: <4A537377.3070506@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49EC00CD.4020205@sun.com> <4A52B0B5.4080801@sun.com> <4A52CBF2.7040101@sun.com> <4A530E6F.8060101@Sun.COM> <4A53704D.2090906@sun.com> <4A5371E7.2060402@Sun.COM> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 2280 Darren J Moffat wrote: > Garrett D'Amore wrote: >> Darren J Moffat wrote: >>> Garrett D'Amore wrote: >>>> Frank Che wrote: >>>>> The project team would like to change the release binding of this >>>>> project from micro to patch, for back-porting purpose. If there is >>>>> any concern on this, please let the project team know. >>>>> >>>>> I think this change is qualified for self review. If there is >>>>> concern, I can upgrade it to a fast track. >>>> >>>> I think since you requested micro binding originally, this is >>>> trivially obvious. Indeed, I think many people these days treat >>>> micro binding as synonymous with patch binding. (We haven't had a >>>> "micro" release since Solaris 2.5.1.) >>>> >>>> For C-Team's point of view, I think you can just go ahead and >>>> proceed as if you originally requested patch binding. >>> >>> There is a very important difference between micro and patch though >>> and that is the delivery mechanism. A micro release can be assumed >>> to be fresh installer or upgraded to but a patch release could need >>> the feature applied by 'patchadd' as well as being upgraded to in a >>> fresh bitted release. This case introduces a new package >>> (SUNWmptsas) so as long as that can be properly dealt with in the >>> patch release train I have no problem with the change of binding. >>> >> >> C-Team is apparently confused... while the driver is intended for the >> feature-patch gate (i.e. for delivery as part of a Solaris 10 >> update), they have made a point of requesting the project go back and >> ask for patch binding. > > I don't think the C-Team is confused. Solaris 10 updates are not > micro releases they are patch binding releases. Solaris 10 updates have been handled the same way all other updates since at least Solaris 8 have been handled, as a collection of patches. So I'm not sure I understand how a micro release would happen.... unless someone did a Solaris 10.1 or somesuch. The last such release I recall was Solaris 2..5.1. Okay, well in this case its obvious enough. In the meantime, I think case submitters (and their sponsors) should refrain from using micro release binding -- its not really what they want. They want either minor or patch binding. -- Garrett From Khanh.Doan@Sun.COM Tue Jul 7 13:39:49 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n67KdmWW028085 for ; Tue, 7 Jul 2009 13:39:48 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n67KdWYp017568 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 8 Jul 2009 04:39:47 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KMF00623IQ9R200@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 13:39:45 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KMF00L43IQ8V2C0@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 13:39:44 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n67KdhaG026869 for ; Tue, 07 Jul 2009 13:39:43 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KMF00L00IG8BF00@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 13:39:43 -0700 (PDT) Received: from [129.146.224.155] ([unknown] [129.146.224.155]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KMF006VCIQ7GWC0@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 13:39:43 -0700 (PDT) Date: Tue, 07 Jul 2009 13:39:00 -0700 From: Khanh Doan Subject: Seek "patch" binding approval for PSARC/2008/443 Sender: Khanh.Doan@Sun.COM To: psarc-ext@Sun.COM, T Paul Lee , Jiang Javen Wu , yongfeng du Cc: John Ojemann , Meggy.Chen@Sun.COM, Patrick Greene Reply-to: Khanh.Doan@Sun.COM Message-id: <4A53B264.8010101@Sun.COM> MIME-version: 1.0 Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.18 (X11/20090209) Status: RO Content-Length: 887
Hi ARC members,

During U8 ON C-team Checklist review for PTL 6129, mpt_sas driver, we were informed by John Ojemann to seek ARC approval for "patch" binding as the current PSARC/2008/443 only seek "micro" release.    This is an oversight in our part since this driver is needed to support LSI SAS 200x and SAS2108 series of chip.   Sun and partners platforms plan to support these HBAs when LSI releases this Sept 2009.  With U8 RR in October, the driver is needed for boot support on some of Sun x86 platforms.

Please approve our request for "patch" binding.

Thanks,
- Khanh






 From Sebastien.Roy@sun.com Tue Jul 7 13:58:00 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n67KvxKx029308 for ; Tue, 7 Jul 2009 13:57:59 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n67Kvf3U022665 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 7 Jul 2009 21:57:58 +0100 (BST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KMF00309JKJLZ00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 14:57:55 -0600 (MDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KMF00B2MJKJUXC0@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 14:57:55 -0600 (MDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n67KvtiC023037 for ; Tue, 07 Jul 2009 20:57:55 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KMF00E00J4NUV00@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 14:57:55 -0600 (MDT) Received: from [129.148.174.103] ([unknown] [129.148.174.103]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KMF006KUJKG5B00@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 14:57:52 -0600 (MDT) Date: Tue, 07 Jul 2009 16:56:31 -0400 From: Sebastien Roy Subject: Re: Seek "patch" binding approval for PSARC/2008/443 In-reply-to: <4A53B264.8010101@Sun.COM> Sender: Sebastien.Roy@sun.com To: Khanh.Doan@sun.com Cc: PSARC-ext@sun.com, T Paul Lee , Jiang Javen Wu , yongfeng du , John Ojemann , Meggy.Chen@sun.com, Patrick Greene Message-id: <1247000191.4458.35.camel@strat> Organization: Sun Microsystems MIME-version: 1.0 X-Mailer: Evolution 2.26.1.1 Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4A53B264.8010101@Sun.COM> Status: RO Content-Length: 738 On Tue, 2009-07-07 at 13:39 -0700, Khanh Doan wrote: > > Hi ARC members, > > During U8 ON C-team Checklist review for PTL 6129, mpt_sas driver, we > were informed by John Ojemann to seek ARC approval for "patch" binding > as the currentPSARC/2008/443 only seek "micro" release. This is an > oversight in our part since this driver is needed to support LSI SAS > 200x and SAS2108 series of chip. Sun and partners platforms plan to > support these HBAs when LSI releases this Sept 2009. With U8 RR in > October, the driver is needed for boot support on some of Sun x86 > platforms. > > Please approve our request for "patch" binding. I don't see anything in the materials that would be inhibitive to a patch binding. +1 -Seb From gdamore@sun.com Tue Jul 7 14:01:25 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n67L1PLN029668 for ; Tue, 7 Jul 2009 14:01:25 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n67L1Kqw025644 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 7 Jul 2009 22:01:24 +0100 (BST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KMF00401JQB0500@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 15:01:23 -0600 (MDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KMF00BVRJQAUYA0@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 15:01:23 -0600 (MDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n67L1HJ1014881 for ; Tue, 07 Jul 2009 14:01:22 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KMF00J00J9DR100@fe-sfbay-10.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 14:01:21 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KMF00938JPWN0C0@fe-sfbay-10.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 07 Jul 2009 14:01:09 -0700 (PDT) Date: Tue, 07 Jul 2009 14:01:08 -0700 From: "Garrett D'Amore" Subject: Re: Seek "patch" binding approval for PSARC/2008/443 In-reply-to: <4A53B264.8010101@Sun.COM> Sender: garrett.damore@sun.com To: Khanh.Doan@sun.com Cc: PSARC-ext@sun.com, T Paul Lee , Jiang Javen Wu , yongfeng du , John Ojemann , Meggy.Chen@sun.com, Patrick Greene Message-id: <4A53B794.6070202@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4A53B264.8010101@Sun.COM> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 861 Khanh Doan wrote: > > Hi ARC members, > > During U8 ON C-team Checklist review for PTL 6129, mpt_sas driver, we > were informed by John Ojemann to seek ARC approval for "patch" binding > as the current PSARC/2008/443 > only seek "micro" > release. This is an oversight in our part since this driver is > needed to support LSI SAS 200x and SAS2108 series of chip. Sun and > partners platforms plan to support these HBAs when LSI releases this > Sept 2009. With U8 RR in October, the driver is needed for boot > support on some of Sun x86 platforms. > > Please approve our request for "patch" binding. > > Thanks, > - Khanh > > > > > > Done. :-) Its good form to wait 24 hours before integrating the change, though, in case someone else raises an objection (unlikely in this case). - Garrett