From Mark.Carlson@sun.com Fri Jan 8 12:51:54 2010 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 o08KpsRm025005 for ; Fri, 8 Jan 2010 12:51:54 -0800 (PST) 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.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o08Kprd8018093 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 8 Jan 2010 12:51:54 -0800 (PST) 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 <0KVY00M0Z4MIB800@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 08 Jan 2010 13:51:54 -0700 (MST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KVY00M134MH8Z00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 08 Jan 2010 13:51:53 -0700 (MST) 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 o08Kpr5c005323 for ; Fri, 08 Jan 2010 20:51:53 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KVY007004AKWP00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 08 Jan 2010 13:51:53 -0700 (MST) Received: from dhcp-ubrm05-241-14.central.sun.com ([unknown] [129.147.241.14]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KVY00BXI4MF1N70@mail-amer.sun.com>; Fri, 08 Jan 2010 13:51:51 -0700 (MST) Date: Fri, 08 Jan 2010 13:51:49 -0700 From: "Mark A. Carlson" Subject: iSER patch binding [PSARC/2010/012 Self Review] Sender: Mark.Carlson@sun.com To: PSARC-ext Cc: Peter Dunlap , Jack Meng Message-id: <4B479AE5.5080101@sun.com> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_mXIJelI4/Wg6xr9Sv9x0+g)" X-PMX-Version: 5.4.1.325704 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 Status: RO Content-Length: 14832 This is a multi-part message in MIME format. --Boundary_(ID_mXIJelI4/Wg6xr9Sv9x0+g) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT I am sponsoring this case for Bing Zhao. It requests a patch binding for iSER, updating PSARC 2008/395 as a result. I do not expect this to be controversial so I have marked it Self Review, but am happy to start a timer if an ARC member so desires or significant discussion ensues. -- mark Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: iSER: iSCSI Extensions for RDMA 1.2. Name of Document Author/Supplier: Bing Zhao 1.3. Date of This Document: 1/08/10 1.3.1. Date this project was conceived: 8/1/07 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: PSARC 1.4.3. The Director/VP who is "Sponsoring" this project: scott.tracy@sun.com 1.4.4. The name of your business unit: Software 1.5. Email Aliases: 1.5.1. Responsible Manager: peter.buckingham@sun.com 1.5.2. Responsible Engineer: peter.dunlap@sun.com 1.5.3. Marketing Manager: margaret.hamburger@sunc.om 1.5.4. Interest List: iser-dev@opensolaris.org 2. Project Summary 2.1. Project Description: iSCSI Extensions for RDMA (iSER) accelerates the iSCSI protocol by mapping the data transfer phases to Remote DMA (RDMA) operations. As a result an iSER initiator should be able to read and write data from an iSER target at high data rates with relatively low CPU utilization compared to iSCSI using TCP/IP. This project will implement both an iSER initiator and an iSER target. In addition, the project will implement an iSCSI port provider (iscsit) for the SCSI Target Mode Framework (STMF) introduced by PSARC 2007/523 adding an iSCSI transport option to the existing Fibre Channel support. The iSER target will be an extension of this iSCSI port provider. 2.2. Risks and Assumptions: This project does not replace the existing iSCSI target (PSARC 2005/441) although it is intended to become the preferred iSCSI target implementation since future SCSI target development will be focused around STMF. 3. Business Summary Solaris currently lacks a high performance low latency storage protocol for Infiniband networks. This is inhibiting the adoption of Solaris in the HPC space which relies heavily on Infiniband. 3.1. Problem Area: Need an Infiniband storage protocol 3.2. Market/Requester: Software 3.3. Business Justification: 3.4. Competitive Analysis: Linux and Windows provide both iSER and iSCSI initiators. Linux provides an iSCSI target implementation as well. 3.5. Opportunity Window/Exposure: 3.6. How will you know when you are done?: Both iSER and software iSCSI transport should provide comparable performance to Linux and Windows offerings on the same hardware as well as interoperating with those same Linux and Windows implementations. 4. Technical Description: 4.1. Details: iSER will be implemented as a pluggable transport capability so that a modified iSCSI initiator and the new iSCSI target can use either TCP/IP transport or iSER (via Infiniband) transport. The case materials describe the approach in more detail. 4.2. Bug/RFE Number(s): 6702584 Need iSCSI port provider for COMSTAR 6702591 COMSTAR iSCSI port provider needs to support iSER transport 4.3. In Scope: Standards compliant iSER initiator and target implementations Standards compliant iSCSI target implementation 4.4. Out of Scope: Integration between the new iSCSI target and ZFS (a future project should address this) 4.5. Interfaces: Imported: libstmf STMF port provider API Exported: itadm CLI for iSCSI target management libiscsit 4.6. Doc Impact: COMSTAR/STMF documentation will need modifications to describe the new iSCSI transport capability. iSCSI documentation will need to be modified to describe configuring iSER connections. 4.7. Admin/Config Impact: The iSCSI administrative tools (iscsiadm(1m) and itadm(1m) in this case) are not expected to require any modifications for iSER. iSER transport is automatically selected for iSCSI connections established on an iSER-capable network. 4.8. HA Impact: N/A 4.9. I18N/L10N Impact: N/A 4.10. Packaging& Delivery: No modifications to existing packages 4.11. Security Impact: The iSCSI target will listen for new iSCSI connections on any port configured by the user (default is 3260). 4.12. Dependencies: No dependencies on other projects 5. Reference Documents: iSER/iSCSI COMSTAR OpenSolaris project page: http://www.opensolaris.org/os/project/iser RFC3720: Internet Small Computer Systems Interface (iSCSI) RFC5046: Internal Small Computer System Interface (iSCSI) Extensions for Remote Direct Memory Access (RDMA) RFC5047: DA: Datamover Architecture for the Internal Small Computer System Interface (iSCSI) PSARC 2007/523 COMSTAR: Common Multiprotocol SCSI Target PSARC 2007/153 iSCSI target provider PSARC 2006/622 iSCSI/ZFS integration PSARC 2005/441 iSCSI Target Project 6. Resources and Schedule: 6.1. Projected Availability: Q1FY09 6.2. Cost of Effort: 5 people for 12 months 6.3. Cost of Capital Resources: $100,000 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: NWS 6.4.3. Type of CPT Review and Approval expected: Standard 6.4.4. Project Boundary Conditions: N/A 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: 6.4.7. Target RTI Date/Release: 9/22/08, targeting build 100 Solaris 10 Update 9 The iSER initiator is required to be backported to S10U9 and needs a patch binding 6.4.8. Target Code Design Review Date: 7/31/08 6.4.9. Update approval addition: N/A 6.5. ARC review type: Standard 6.6. ARC Exposure: Open 7. Prototype Availability: 7.1. Prototype Availability: iSCSI target prototype was available 4/25/08 iSER initiator and target should be available 7/1/08 7.2. Prototype Cost: N/A --Boundary_(ID_mXIJelI4/Wg6xr9Sv9x0+g) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT 
I am sponsoring this case for Bing Zhao. It requests a patch
binding for iSER, updating PSARC 2008/395 as a result.
I do not expect this to be controversial so I have marked it
Self Review, but am happy to start a timer if an ARC member
so desires or significant discussion ensues.

-- mark

Template Version: @(#)onepager.txt 1.35 07/11/07 SMI
Copyright 2008 Sun Microsystems

1. Introduction
   1.1. Project/Component Working Name:
       iSER: iSCSI Extensions for RDMA

   1.2. Name of Document Author/Supplier:
       Bing Zhao

   1.3. Date of This Document:
       1/08/10
    
    1.3.1. Date this project was conceived:
           8/1/07

   1.4. Name of Major Document Customer(s)/Consumer(s):
    1.4.1. The PAC or CPT you expect to review your project:
           Solaris PAC
    1.4.2. The ARC(s) you expect to review your project:
           PSARC
    1.4.3. The Director/VP who is "Sponsoring" this project:
           scott.tracy@sun.com
    1.4.4. The name of your business unit:
           Software

   1.5. Email Aliases:
        1.5.1. Responsible Manager: peter.buckingham@sun.com
        1.5.2. Responsible Engineer: peter.dunlap@sun.com
        1.5.3. Marketing Manager: margaret.hamburger@sunc.om
    1.5.4. Interest List: iser-dev@opensolaris.org

2. Project Summary
   2.1. Project Description:

       iSCSI Extensions for RDMA (iSER) accelerates the iSCSI protocol by
       mapping the data transfer phases to Remote DMA (RDMA) operations. 
       As a result an iSER initiator should be able to read and write data 
       from an iSER target at high data rates with relatively low CPU
       utilization compared to iSCSI using TCP/IP. This project will implement
       both an iSER initiator and an iSER target. In addition, the project will
       implement an iSCSI port provider (iscsit) for the SCSI Target Mode
       Framework (STMF) introduced by PSARC 2007/523 adding an iSCSI transport
       option to the existing Fibre Channel support. The iSER target will be an 
       extension of this iSCSI port provider.

   2.2. Risks and Assumptions:

       This project does not replace the existing iSCSI target (PSARC 2005/441)
       although it is intended to become the preferred iSCSI target
       implementation since future SCSI target development will be focused
       around STMF.

3. Business Summary

       Solaris currently lacks a high performance low latency storage protocol
       for Infiniband networks.  This is inhibiting the adoption of Solaris in
       the HPC space which relies heavily on Infiniband.

   3.1. Problem Area:

       Need an Infiniband storage protocol

   3.2. Market/Requester:

       Software

   3.3. Business Justification:

   3.4. Competitive Analysis:

       Linux and Windows provide both iSER and iSCSI initiators.  Linux
       provides an iSCSI target implementation as well.

   3.5. Opportunity Window/Exposure:

   3.6. How will you know when you are done?:

       Both iSER and software iSCSI transport should provide comparable
       performance to Linux and Windows offerings on the same hardware as
       well as interoperating with those same Linux and Windows
       implementations.
    
4. Technical Description:
    4.1. Details:

        iSER will be implemented as a pluggable transport capability so
        that a modified iSCSI initiator and the new iSCSI target can use
        either TCP/IP transport or iSER (via Infiniband) transport.

        The case materials describe the approach in more detail.

    4.2. Bug/RFE Number(s):
        6702584 Need iSCSI port provider for COMSTAR
        6702591 COMSTAR iSCSI port provider needs to support iSER transport

    4.3. In Scope:
        Standards compliant iSER initiator and target implementations
        Standards compliant iSCSI target implementation

    4.4. Out of Scope:
        Integration between the new iSCSI target and ZFS (a future project
        should address this)
    
    4.5. Interfaces:
        Imported:
            libstmf
            STMF port provider API
        Exported:
            itadm CLI for iSCSI target management
            libiscsit
    
    4.6. Doc Impact:
        COMSTAR/STMF documentation will need modifications to describe the
        new iSCSI transport capability.

        iSCSI documentation will need to be modified to describe
        configuring iSER connections.
    
    4.7. Admin/Config Impact:
        The iSCSI administrative tools (iscsiadm(1m) and itadm(1m) in this
        case) are not expected to require any modifications for iSER.
        iSER transport is automatically selected for iSCSI connections
        established on an iSER-capable network.
    
    4.8. HA Impact:
        N/A
    
    4.9. I18N/L10N Impact:
        N/A
    
    4.10. Packaging & Delivery:
        No modifications to existing packages
    
    4.11. Security Impact:
        The iSCSI target will listen for new iSCSI connections on any port
        configured by the user (default is 3260).

    4.12. Dependencies:
        No dependencies on other projects

5. Reference Documents:
    iSER/iSCSI COMSTAR OpenSolaris project page:
             http://www.opensolaris.org/os/project/iser

    RFC3720: Internet Small Computer Systems Interface (iSCSI)

    RFC5046: Internal Small Computer System Interface (iSCSI)
    Extensions for Remote Direct Memory Access (RDMA)

    RFC5047: DA: Datamover Architecture for the Internal Small
    Computer System Interface (iSCSI)

    PSARC 2007/523 COMSTAR: Common Multiprotocol SCSI Target

    PSARC 2007/153 iSCSI target provider

    PSARC 2006/622 iSCSI/ZFS integration

    PSARC 2005/441 iSCSI Target Project

6. Resources and Schedule:
   6.1. Projected Availability:
       Q1FY09

   6.2. Cost of Effort:
       5 people for 12 months

   6.3. Cost of Capital Resources:
       $100,000

   6.4. Product Approval Committee requested information:
       6.4.1. Consolidation or Component Name:
           NWS
    6.4.3. Type of CPT Review and Approval expected:
           Standard
        6.4.4. Project Boundary Conditions:
           N/A
    6.4.5. Is this a necessary project for OEM agreements:
           No
    6.4.6. Notes:
    6.4.7. Target RTI Date/Release:
           9/22/08, targeting build 100
	   Solaris 10 Update 9
	   The iSER initiator is required to be backported to S10U9 and
           needs a patch binding
    6.4.8. Target Code Design Review Date: 7/31/08
    6.4.9. Update approval addition:
           N/A

   6.5. ARC review type:
       Standard

   6.6. ARC Exposure:
       Open

7. Prototype Availability:
   7.1. Prototype Availability:
       iSCSI target prototype was available 4/25/08
       iSER initiator and target should be available 7/1/08

   7.2. Prototype Cost:
       N/A
--Boundary_(ID_mXIJelI4/Wg6xr9Sv9x0+g)-- From John.Fischer@Sun.COM Mon Jan 11 10:23:09 2010 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 o0BIN9Ax001237 for ; Mon, 11 Jan 2010 10:23:09 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o0BIN97g006223 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 11 Jan 2010 10:23:09 -0800 (PST) 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 <0KW300I0PHQLNL00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 11 Jan 2010 11:23:09 -0700 (MST) 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 <0KW300DQVHQK1D40@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 11 Jan 2010 11:23:08 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o0BIN8LM015109 for ; Mon, 11 Jan 2010 18:23:08 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KW300K00H473300@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 11 Jan 2010 11:23:08 -0700 (MST) Received: from [192.168.10.9] ([unknown] [76.20.56.122]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KW3002RIHQ7LPE0@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 11 Jan 2010 11:22:55 -0700 (MST) Date: Mon, 11 Jan 2010 10:22:41 -0800 From: John Fischer Subject: Re: iSER patch binding [PSARC/2010/012 Self Review] In-reply-to: <4B479AE5.5080101@sun.com> Sender: John.Fischer@Sun.COM To: "Mark A. Carlson" Cc: PSARC-ext , Jack Meng , Peter Dunlap Reply-to: John.Fischer@Sun.COM Message-id: <4B4B6C71.7080104@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: <4B479AE5.5080101@sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091124) Status: RO Content-Length: 7634 Bing, Am I to assume that the interfaces listed in section 4.5 are Committed? > 4.5. Interfaces: > Imported: > libstmf > STMF port provider API > Exported: > itadm CLI for iSCSI target management > libiscsit Thanks, John Mark A. Carlson wrote: > I am sponsoring this case for Bing Zhao. It requests a patch > binding for iSER, updating PSARC 2008/395 as a result. > I do not expect this to be controversial so I have marked it > Self Review, but am happy to start a timer if an ARC member > so desires or significant discussion ensues. > > -- mark > > Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > Copyright 2008 Sun Microsystems > > 1. Introduction > 1.1. Project/Component Working Name: > iSER: iSCSI Extensions for RDMA > > 1.2. Name of Document Author/Supplier: > Bing Zhao > > 1.3. Date of This Document: > 1/08/10 > > 1.3.1. Date this project was conceived: > 8/1/07 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > Solaris PAC > 1.4.2. The ARC(s) you expect to review your project: > PSARC > 1.4.3. The Director/VP who is "Sponsoring" this project: > scott.tracy@sun.com > 1.4.4. The name of your business unit: > Software > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: peter.buckingham@sun.com > 1.5.2. Responsible Engineer: peter.dunlap@sun.com > 1.5.3. Marketing Manager: margaret.hamburger@sunc.om > 1.5.4. Interest List: iser-dev@opensolaris.org > > 2. Project Summary > 2.1. Project Description: > > iSCSI Extensions for RDMA (iSER) accelerates the iSCSI protocol by > mapping the data transfer phases to Remote DMA (RDMA) operations. > As a result an iSER initiator should be able to read and write data > from an iSER target at high data rates with relatively low CPU > utilization compared to iSCSI using TCP/IP. This project will > implement > both an iSER initiator and an iSER target. In addition, the > project will > implement an iSCSI port provider (iscsit) for the SCSI Target Mode > Framework (STMF) introduced by PSARC 2007/523 adding an iSCSI > transport > option to the existing Fibre Channel support. The iSER target > will be an > extension of this iSCSI port provider. > > 2.2. Risks and Assumptions: > > This project does not replace the existing iSCSI target (PSARC > 2005/441) > although it is intended to become the preferred iSCSI target > implementation since future SCSI target development will be focused > around STMF. > > 3. Business Summary > > Solaris currently lacks a high performance low latency storage > protocol > for Infiniband networks. This is inhibiting the adoption of > Solaris in > the HPC space which relies heavily on Infiniband. > > 3.1. Problem Area: > > Need an Infiniband storage protocol > > 3.2. Market/Requester: > > Software > > 3.3. Business Justification: > > 3.4. Competitive Analysis: > > Linux and Windows provide both iSER and iSCSI initiators. Linux > provides an iSCSI target implementation as well. > > 3.5. Opportunity Window/Exposure: > > 3.6. How will you know when you are done?: > > Both iSER and software iSCSI transport should provide comparable > performance to Linux and Windows offerings on the same hardware as > well as interoperating with those same Linux and Windows > implementations. > > 4. Technical Description: > 4.1. Details: > > iSER will be implemented as a pluggable transport capability so > that a modified iSCSI initiator and the new iSCSI target can use > either TCP/IP transport or iSER (via Infiniband) transport. > > The case materials describe the approach in more detail. > > 4.2. Bug/RFE Number(s): > 6702584 Need iSCSI port provider for COMSTAR > 6702591 COMSTAR iSCSI port provider needs to support iSER transport > > 4.3. In Scope: > Standards compliant iSER initiator and target implementations > Standards compliant iSCSI target implementation > > 4.4. Out of Scope: > Integration between the new iSCSI target and ZFS (a future project > should address this) > > 4.5. Interfaces: > Imported: > libstmf > STMF port provider API > Exported: > itadm CLI for iSCSI target management > libiscsit > > 4.6. Doc Impact: > COMSTAR/STMF documentation will need modifications to describe the > new iSCSI transport capability. > > iSCSI documentation will need to be modified to describe > configuring iSER connections. > > 4.7. Admin/Config Impact: > The iSCSI administrative tools (iscsiadm(1m) and itadm(1m) in this > case) are not expected to require any modifications for iSER. > iSER transport is automatically selected for iSCSI connections > established on an iSER-capable network. > > 4.8. HA Impact: > N/A > > 4.9. I18N/L10N Impact: > N/A > > 4.10. Packaging& Delivery: > No modifications to existing packages > > 4.11. Security Impact: > The iSCSI target will listen for new iSCSI connections on any port > configured by the user (default is 3260). > > 4.12. Dependencies: > No dependencies on other projects > > 5. Reference Documents: > iSER/iSCSI COMSTAR OpenSolaris project page: > http://www.opensolaris.org/os/project/iser > > RFC3720: Internet Small Computer Systems Interface (iSCSI) > > RFC5046: Internal Small Computer System Interface (iSCSI) > Extensions for Remote Direct Memory Access (RDMA) > > RFC5047: DA: Datamover Architecture for the Internal Small > Computer System Interface (iSCSI) > > PSARC 2007/523 COMSTAR: Common Multiprotocol SCSI Target > > PSARC 2007/153 iSCSI target provider > > PSARC 2006/622 iSCSI/ZFS integration > > PSARC 2005/441 iSCSI Target Project > > 6. Resources and Schedule: > 6.1. Projected Availability: > Q1FY09 > > 6.2. Cost of Effort: > 5 people for 12 months > > 6.3. Cost of Capital Resources: > $100,000 > > 6.4. Product Approval Committee requested information: > 6.4.1. Consolidation or Component Name: > NWS > 6.4.3. Type of CPT Review and Approval expected: > Standard > 6.4.4. Project Boundary Conditions: > N/A > 6.4.5. Is this a necessary project for OEM agreements: > No > 6.4.6. Notes: > 6.4.7. Target RTI Date/Release: > 9/22/08, targeting build 100 > Solaris 10 Update 9 > The iSER initiator is required to be backported to S10U9 and > needs a patch binding > 6.4.8. Target Code Design Review Date: 7/31/08 > 6.4.9. Update approval addition: > N/A > > 6.5. ARC review type: > Standard > > 6.6. ARC Exposure: > Open > > 7. Prototype Availability: > 7.1. Prototype Availability: > iSCSI target prototype was available 4/25/08 > iSER initiator and target should be available 7/1/08 > > 7.2. Prototype Cost: > N/A > > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org From Bing.Zhao@sun.com Tue Jan 12 18:49:30 2010 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 o0D2nUvF018703 for ; Tue, 12 Jan 2010 18:49:30 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.4) with ESMTP id o0D2nSNj007353 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 12 Jan 2010 19:49:30 -0700 (MST) 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 <0KW50060DZUHIW00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 12 Jan 2010 18:49:29 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KW5003UCZUGIN20@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 12 Jan 2010 18:49:29 -0800 (PST) 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 o0D2nSLk007702 for ; Wed, 13 Jan 2010 02:49:28 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KW500M00ZTZHQ00@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 13 Jan 2010 10:49:28 +0800 (SGT) Received: from [129.158.144.200] ([unknown] [129.158.144.200]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KW500DAYZUES150@mail-apac.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 13 Jan 2010 10:49:28 +0800 (SGT) Date: Wed, 13 Jan 2010 10:50:49 +0800 From: Bing Zhao - Sun Microsystems Subject: Re: iSER patch binding [PSARC/2010/012 Self Review] In-reply-to: <4B4B6C71.7080104@sun.com> Sender: Bing.Zhao@sun.com To: John.Fischer@sun.com Cc: "Mark A. Carlson" , PSARC-ext , Jack Meng , Peter Dunlap Message-id: <4B4D3509.1030202@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: <4B479AE5.5080101@sun.com> <4B4B6C71.7080104@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20090223) Status: RO Content-Length: 8288 Hi John: Thank you very much for your response. Please see 6.4.7: 6.4.7. Target RTI Date/Release: 9/22/08, targeting build 100 Solaris 10 Update 9 The iSER initiator is required to be backported to S10U9 and needs a patch binding This patch binding is only for iser initiator side. It doesn't contain iscsit, itadm, stmf or any target related things. Regards, Bing John Fischer wrote: > Bing, > > Am I to assume that the interfaces listed in section 4.5 are Committed? > >> 4.5. Interfaces: >> Imported: >> libstmf >> STMF port provider API >> Exported: >> itadm CLI for iSCSI target management >> libiscsit > > Thanks, > > John > > Mark A. Carlson wrote: >> I am sponsoring this case for Bing Zhao. It requests a patch >> binding for iSER, updating PSARC 2008/395 as a result. >> I do not expect this to be controversial so I have marked it >> Self Review, but am happy to start a timer if an ARC member >> so desires or significant discussion ensues. >> >> -- mark >> >> Template Version: @(#)onepager.txt 1.35 07/11/07 SMI >> Copyright 2008 Sun Microsystems >> >> 1. Introduction >> 1.1. Project/Component Working Name: >> iSER: iSCSI Extensions for RDMA >> >> 1.2. Name of Document Author/Supplier: >> Bing Zhao >> >> 1.3. Date of This Document: >> 1/08/10 >> >> 1.3.1. Date this project was conceived: >> 8/1/07 >> >> 1.4. Name of Major Document Customer(s)/Consumer(s): >> 1.4.1. The PAC or CPT you expect to review your project: >> Solaris PAC >> 1.4.2. The ARC(s) you expect to review your project: >> PSARC >> 1.4.3. The Director/VP who is "Sponsoring" this project: >> scott.tracy@sun.com >> 1.4.4. The name of your business unit: >> Software >> >> 1.5. Email Aliases: >> 1.5.1. Responsible Manager: peter.buckingham@sun.com >> 1.5.2. Responsible Engineer: peter.dunlap@sun.com >> 1.5.3. Marketing Manager: margaret.hamburger@sunc.om >> 1.5.4. Interest List: iser-dev@opensolaris.org >> >> 2. Project Summary >> 2.1. Project Description: >> >> iSCSI Extensions for RDMA (iSER) accelerates the iSCSI >> protocol by >> mapping the data transfer phases to Remote DMA (RDMA) operations. >> As a result an iSER initiator should be able to read and write >> data >> from an iSER target at high data rates with relatively low CPU >> utilization compared to iSCSI using TCP/IP. This project will >> implement >> both an iSER initiator and an iSER target. In addition, the >> project will >> implement an iSCSI port provider (iscsit) for the SCSI Target >> Mode >> Framework (STMF) introduced by PSARC 2007/523 adding an iSCSI >> transport >> option to the existing Fibre Channel support. The iSER target >> will be an >> extension of this iSCSI port provider. >> >> 2.2. Risks and Assumptions: >> >> This project does not replace the existing iSCSI target (PSARC >> 2005/441) >> although it is intended to become the preferred iSCSI target >> implementation since future SCSI target development will be >> focused >> around STMF. >> >> 3. Business Summary >> >> Solaris currently lacks a high performance low latency storage >> protocol >> for Infiniband networks. This is inhibiting the adoption of >> Solaris in >> the HPC space which relies heavily on Infiniband. >> >> 3.1. Problem Area: >> >> Need an Infiniband storage protocol >> >> 3.2. Market/Requester: >> >> Software >> >> 3.3. Business Justification: >> >> 3.4. Competitive Analysis: >> >> Linux and Windows provide both iSER and iSCSI initiators. Linux >> provides an iSCSI target implementation as well. >> >> 3.5. Opportunity Window/Exposure: >> >> 3.6. How will you know when you are done?: >> >> Both iSER and software iSCSI transport should provide comparable >> performance to Linux and Windows offerings on the same >> hardware as >> well as interoperating with those same Linux and Windows >> implementations. >> >> 4. Technical Description: >> 4.1. Details: >> >> iSER will be implemented as a pluggable transport capability so >> that a modified iSCSI initiator and the new iSCSI target can use >> either TCP/IP transport or iSER (via Infiniband) transport. >> >> The case materials describe the approach in more detail. >> >> 4.2. Bug/RFE Number(s): >> 6702584 Need iSCSI port provider for COMSTAR >> 6702591 COMSTAR iSCSI port provider needs to support iSER >> transport >> >> 4.3. In Scope: >> Standards compliant iSER initiator and target implementations >> Standards compliant iSCSI target implementation >> >> 4.4. Out of Scope: >> Integration between the new iSCSI target and ZFS (a future >> project >> should address this) >> >> 4.5. Interfaces: >> Imported: >> libstmf >> STMF port provider API >> Exported: >> itadm CLI for iSCSI target management >> libiscsit >> >> 4.6. Doc Impact: >> COMSTAR/STMF documentation will need modifications to >> describe the >> new iSCSI transport capability. >> >> iSCSI documentation will need to be modified to describe >> configuring iSER connections. >> >> 4.7. Admin/Config Impact: >> The iSCSI administrative tools (iscsiadm(1m) and itadm(1m) in >> this >> case) are not expected to require any modifications for iSER. >> iSER transport is automatically selected for iSCSI connections >> established on an iSER-capable network. >> >> 4.8. HA Impact: >> N/A >> >> 4.9. I18N/L10N Impact: >> N/A >> >> 4.10. Packaging& Delivery: >> No modifications to existing packages >> >> 4.11. Security Impact: >> The iSCSI target will listen for new iSCSI connections on any >> port >> configured by the user (default is 3260). >> >> 4.12. Dependencies: >> No dependencies on other projects >> >> 5. Reference Documents: >> iSER/iSCSI COMSTAR OpenSolaris project page: >> http://www.opensolaris.org/os/project/iser >> >> RFC3720: Internet Small Computer Systems Interface (iSCSI) >> >> RFC5046: Internal Small Computer System Interface (iSCSI) >> Extensions for Remote Direct Memory Access (RDMA) >> >> RFC5047: DA: Datamover Architecture for the Internal Small >> Computer System Interface (iSCSI) >> >> PSARC 2007/523 COMSTAR: Common Multiprotocol SCSI Target >> >> PSARC 2007/153 iSCSI target provider >> >> PSARC 2006/622 iSCSI/ZFS integration >> >> PSARC 2005/441 iSCSI Target Project >> >> 6. Resources and Schedule: >> 6.1. Projected Availability: >> Q1FY09 >> >> 6.2. Cost of Effort: >> 5 people for 12 months >> >> 6.3. Cost of Capital Resources: >> $100,000 >> >> 6.4. Product Approval Committee requested information: >> 6.4.1. Consolidation or Component Name: >> NWS >> 6.4.3. Type of CPT Review and Approval expected: >> Standard >> 6.4.4. Project Boundary Conditions: >> N/A >> 6.4.5. Is this a necessary project for OEM agreements: >> No >> 6.4.6. Notes: >> 6.4.7. Target RTI Date/Release: >> 9/22/08, targeting build 100 >> Solaris 10 Update 9 >> The iSER initiator is required to be backported to S10U9 and >> needs a patch binding >> 6.4.8. Target Code Design Review Date: 7/31/08 >> 6.4.9. Update approval addition: >> N/A >> >> 6.5. ARC review type: >> Standard >> >> 6.6. ARC Exposure: >> Open >> >> 7. Prototype Availability: >> 7.1. Prototype Availability: >> iSCSI target prototype was available 4/25/08 >> iSER initiator and target should be available 7/1/08 >> >> 7.2. Prototype Cost: >> N/A >> >> >> _______________________________________________ >> opensolaris-arc mailing list >> opensolaris-arc@opensolaris.org