From sacadmin Tue Apr 11 20:08:26 2006 Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.12.9+Sun/8.12.9) with ESMTP id k3C38QIQ019205; Tue, 11 Apr 2006 20:08:26 -0700 (PDT) Received: (from taylor@localhost) by sac.sfbay.sun.com (8.12.9+Sun/8.12.9/Submit) id k3C38QjZ019201; Tue, 11 Apr 2006 20:08:26 -0700 (PDT) Date: Tue, 11 Apr 2006 20:08:26 -0700 (PDT) From: Eric Taylor Message-Id: <200604120308.k3C38QjZ019201@sac.sfbay.sun.com> To: PSARC@sac.sfbay.sun.com Cc: Eric.Taylor@Sun.COM Subject: scsa dma enhancement [PSARC/2006/240 Timeout: 04/18/2006] Status: RO Content-Length: 3107 Subject: PSARC FastTrack [04/18/2006]: scsa dma enhancement I am sponsoring this fastrack for myself, with a release binding of "minor." I've put sample man pages in the materials subdirectory. Thanks, Eric Template Version: @(#)sac_nextcase 1.56 10/26/05 SMI This information is Copyright 2006 Sun Microsystems, Inc. 1. Introduction 1.1. Project/Component Working Name: scsa dma enhancement 1.2. Name of Document Author/Supplier: Author: Eric Taylor 1.3 Date of This Document: 11 April, 2006 4. Technical Description Summary ------- This fast-track modifies the contract private interfaces introduced through 2005/680 so that SCSA can do DMA resource allocation and breakup on behalf of the HBA driver. It also raises the commitment level to evolving. Proposal -------- 2005/680 introduced a kmem_cache mechanism which provided initial- ized scsi_pkt's to HBA drivers. We can take this a step further and have SCSA handle DMA resource allocation and breakup on behalf of the HBA driver. The effect of this is that SCSA hands the HBA driver an array of DMA cookies, so an HBA driver that uses this interface does not need to bind DMA resources, manage partial DMA mappings, etc.; it also obviates the need for the HBA driver to provide tran_dmafree and tran_sync_pkt entry points. This proposal removes the "tran_setup_bp" entry point and adds three new fields to the scsi_pkt structure, which describe the number of DMA cookies, a pointer to the DMA cookie array, etc. Instead of doing allocation and setup, the HBA driver examines the array of DMA cookies in the scsi_pkt at tran_start time, and then programs them into its DMA engine. Man pages are attached, with changebars where it differs from 2005/680. There are no changes to scsi_hba_attach; it is included again for reference. Interface Table: ---------------- exported: INTERFACE STABILITY COMMENTS tran_setup_pkt evolving scsi_hba_tran_t struct member tran_teardown_pkt evolving scsi_hba_tran_t struct member tran_pkt_constructor evolving scsi_hba_tran_t struct member tran_pkt_destructor evolving scsi_hba_tran_t struct member tran_hba_len evolving scsi_hba_tran_t struct member pkt_cdblen evolving scsi_pkt struct member pkt_scblen evolving scsi_pkt struct member pkt_tgtlen evolving scsi_pkt struct member pkt_numcookies evolving scsi_pkt struct member pkt_cookies evolving scsi_pkt struct member pkt_dma_flags evolving scsi_pkt struct member SCSI_HBA_TRAN_CDB evolving scsi_hba_attach flag SCSI_HBA_TRAN_SCB evolving scsi_hba_attach flag imported: INTERFACE STABILITY COMMENTS DDI_DMA_* flags evolving see ddi_dma_buf_bind_handle(9f) Release Binding: --------------- Minor. 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: on 6.5. ARC review type: FastTrack From sacadmin Wed Apr 26 07:12:16 2006 Received: from sfbaymail1sca.SFBay.Sun.COM (sfbaymail1sca.SFBay.Sun.COM [129.145.154.35]) by sac.sfbay.sun.com (8.12.9+Sun/8.12.9) with ESMTP id k3QECGIQ004068 for ; Wed, 26 Apr 2006 07:12:16 -0700 (PDT) Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34]) by sfbaymail1sca.SFBay.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id k3QECGoc006929 for ; Wed, 26 Apr 2006 07:12:16 -0700 (PDT) Received: from fe-amer-03.sun.com ([192.18.108.177]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id k3QECFaN024495 for ; Wed, 26 Apr 2006 08:12:16 -0600 (MDT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0IYC006012298500@mail-amer.sun.com> (original mail from Eric.Taylor@Sun.COM) for PSARC@sac.sfbay.sun.com; Wed, 26 Apr 2006 08:12:15 -0600 (MDT) Received: from Sun.COM ([172.20.58.60]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0IYC003SE24FA120@mail-amer.sun.com> for PSARC@sac.sfbay.sun.com; Wed, 26 Apr 2006 08:12:15 -0600 (MDT) Date: Wed, 26 Apr 2006 08:10:51 -0600 From: eric taylor Subject: Re: scsa dma enhancement [PSARC/2006/240 Timeout: 04/18/2006] In-reply-to: <200604120308.k3C38QjZ019201@sac.sfbay.sun.com> Sender: Eric.Taylor@Sun.COM To: PSARC@sac.sfbay.sun.com Reply-to: Eric.Taylor@Sun.COM Message-id: <444F7F6B.4090900@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <200604120308.k3C38QjZ019201@sac.sfbay.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20041214 Status: RO Content-Length: 3404 This case has timed out with no comments. I am marking it approved. - Eric Eric Taylor wrote On 04/11/06 21:08,: > Subject: PSARC FastTrack [04/18/2006]: scsa dma enhancement > > I am sponsoring this fastrack for myself, with a release > binding of "minor." I've put sample man pages in the > materials subdirectory. > > Thanks, > Eric > > Template Version: @(#)sac_nextcase 1.56 10/26/05 SMI > This information is Copyright 2006 Sun Microsystems, Inc. > 1. Introduction > 1.1. Project/Component Working Name: > scsa dma enhancement > 1.2. Name of Document Author/Supplier: > Author: Eric Taylor > 1.3 Date of This Document: > 11 April, 2006 > 4. Technical Description > > Summary > ------- > This fast-track modifies the contract private interfaces introduced > through 2005/680 so that SCSA can do DMA resource allocation and > breakup on behalf of the HBA driver. It also raises the commitment > level to evolving. > > Proposal > -------- > > 2005/680 introduced a kmem_cache mechanism which provided initial- > ized scsi_pkt's to HBA drivers. We can take this a step further > and have SCSA handle DMA resource allocation and breakup on behalf > of the HBA driver. The effect of this is that SCSA hands the HBA > driver an array of DMA cookies, so an HBA driver that uses this > interface does not need to bind DMA resources, manage partial DMA > mappings, etc.; it also obviates the need for the HBA driver to > provide tran_dmafree and tran_sync_pkt entry points. > > This proposal removes the "tran_setup_bp" entry point and adds three > new fields to the scsi_pkt structure, which describe the number of > DMA cookies, a pointer to the DMA cookie array, etc. Instead of > doing allocation and setup, the HBA driver examines the array of DMA > cookies in the scsi_pkt at tran_start time, and then programs them > into its DMA engine. > > Man pages are attached, with changebars where it differs from > 2005/680. There are no changes to scsi_hba_attach; it is included > again for reference. > > Interface Table: > ---------------- > > exported: > > INTERFACE STABILITY COMMENTS > > tran_setup_pkt evolving scsi_hba_tran_t struct member > tran_teardown_pkt evolving scsi_hba_tran_t struct member > tran_pkt_constructor evolving scsi_hba_tran_t struct member > tran_pkt_destructor evolving scsi_hba_tran_t struct member > tran_hba_len evolving scsi_hba_tran_t struct member > > pkt_cdblen evolving scsi_pkt struct member > pkt_scblen evolving scsi_pkt struct member > pkt_tgtlen evolving scsi_pkt struct member > pkt_numcookies evolving scsi_pkt struct member > pkt_cookies evolving scsi_pkt struct member > pkt_dma_flags evolving scsi_pkt struct member > > SCSI_HBA_TRAN_CDB evolving scsi_hba_attach flag > SCSI_HBA_TRAN_SCB evolving scsi_hba_attach flag > > imported: > > INTERFACE STABILITY COMMENTS > > DDI_DMA_* flags evolving see ddi_dma_buf_bind_handle(9f) > > Release Binding: > --------------- > Minor. > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > on > 6.5. ARC review type: FastTrack