From cth@sac.sfbay.sun.com Thu Feb 12 17:14:37 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 n1D1Eb4E024265 for ; Thu, 12 Feb 2009 17:14:37 -0800 (PST) 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 n1D1Ebi0025102; Thu, 12 Feb 2009 18:14:37 -0700 (MST) 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 <0KEZ00B01CSCA100@nwk-avmta-1.sfbay.Sun.COM>; Thu, 12 Feb 2009 17:14:36 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEZ000M5CSCAF30@nwk-avmta-1.sfbay.Sun.COM>; Thu, 12 Feb 2009 17:14:36 -0800 (PST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1D1EaU5064026; Thu, 12 Feb 2009 17:14:36 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1D1EZv3024260; Thu, 12 Feb 2009 17:14:35 -0800 (PST) Received: (from cth@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n1D1EZg8024256; Thu, 12 Feb 2009 17:14:35 -0800 (PST) Date: Thu, 12 Feb 2009 17:14:35 -0800 (PST) From: Christopher Horne Subject: ndi flavors [PSARC/2009/102 Self Review] To: PSARC-ext@sun.com Cc: scsav3-eng@sun.com Message-id: <200902130114.n1D1EZg8024256@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 7472 I am sponsoring the following fasttrack for Matthew Jacob. Micro/patch binding is requested. I believe the case qualifies for self review (since all the interfaces are Consolidation Private) and have filed it as Closed Approved Automatic. If there is a request, I'd be happy to convert it to a fasttrack and set the timer to enable further discussion. -Chris 1. Introduction 1.1. Project/Component Working Name: ndi flavors 1.2. Name of Document Author/Supplier: Author: Matthew Jacob 1.3. Date of This Document: Tue Feb 10 11:47:14 PST 2009 4. Technical Description 4.1 Background: Associated with each device node is private data that may be accessed via ddi_[gs]et_private_state(9F). The meaning of that data is known to the driver that sets such data, but also by other parts of the system where (formal or otherwise) contracts have established what this private data points to. 4.2 Problem: One example of this is the usage of SCSA HBA nexus drivers' private data pointer by common framework SCSA code. This contains a pointer to a scsi_hba_tran(9S) structure. This is well known amongst multiple parts of the system. This becomes a problem when a SCSA HBA nexus driver needs to support more than just one kind (flavor) of child (i.e. more that just scsi_device(9S) children). Where does the nexus store information relevant to a specific kind (flavor) of child? A previous attempt has been made to address this problem via extensions to the scsi_hba_tran(9S) structure [1]. However, this only provided an out for one additional flavor of child, and for SCSA only. Additionally, code complexity was added by requiring indirection through the existing unrelated structure with various ad hoc mechanisms for determining when such dereference was needed. 4.3 Proposal: The proposal is to allow a nexus driver to declare, at attach time, how many flavors of children they support and to ask the DDI framework to create private pointer storage for any flavors beyond the standard vanilla flavor (which uses the existing ddi_[gs]et_private_state(9F) private data storage mechanism). The proposal also provides interfaces so a nexus driver can set the flavor of its children. Then, in any code that requires child flavor-specific private data held in the nexus to be retrieved, the child's flavor can be used to select the correct private data. The number of flavors for each nexus driver is generally up to that nexus driver. However, in the case of SCSA HBA drivers, the SCSA framework itself will define a specific set of flavors and what they mean. The initial putback of the new interfaces will convert the SMP support delivered by [1] to use the new ndi_flavor* interfaces as well as extend the SMP attach framework to be more of a peer to the SCSI attach framework. In addition, SCSA work in progress will be using the ndi_flavor* interfaces to identify device nodes associated with the dynamic enumeration of initiator ports (ala mscsi/iport). 4.4 Proposed Interfaces: ------------------------------------------------------------------ Interface Name Comm.Lev. Comments ------------------------------------------------------------------ ndi_flavorv_alloc() Cons.Private allocate extra flavor pointer storage ndi_flavorv_set() " set private data pointer for a specific flavor ndi_flavorv_get() " get "" ndi_flavor_set() " set the flavor of a dip (the child) ndi_flavor_get() " get the flavor of a dip (the child) sas_hba_tran_t " SMP specific transport structure smp_tran_alloc() " allocate an SMP specific transport structure smp_attach_setup() " attach and set up an allocated SMP transport structure smp_tran_free() " free an SMP transport structure 4.5 Interface Prototypes: Defined in sunndi.h: void ndi_flavorv_alloc(dev_info_t *, int); void ndi_flavorv_set(dev_info_t *, ndi_flavor_t, void *); void *ndi_flavorv_get(dev_info_t *, ndi_flavor_t); void ndi_flavor_set(dev_info_t *, ndi_flavor_t); ndi_flavor_t ndi_flavor_get(dev_info_t *); NOTE: It is not an error to call ndi_flavorv_alloc() multiple times as long as the number of defined flavors stays the same. NOTE: there is no ndi_flavorv_free() function as the underlying framework will free any allocations when the dev_info detaches. Defined in sas_transport.h: sas_hba_tran_t *sas_hba_tran_alloc(dev_info_t *dip, int flags); int sas_hba_attach_setup(dev_info_t *dip, sas_hba_tran_t *smp); void sas_hba_tran_free(sas_hba_tran_t *smp); 4.4 SCSA Example (fragments): All HBA drivers, from their attach(9E) implementation, call scsi_hba_tran_alloc(9F) (or sas_hba_tran_alloc()). In the SCSA framework code implementing *_tran_alloc() two things happen. First, the *_tran_alloc() implementation may call ndi_flavorv_alloc() to reserve space for all SCSA supported flavors. Second, ndi_flavor_set() will be called to plumb *_tran_alloc()'s flavor of tran. Storage allocated by the ndi_flavorv_alloc() call will be freed by the IO framework when the node detaches. When a child of a non-SCSAv3 HBA driver is created via bus_config operations, the flavor of the child may be set: if (child_is_smp) { ndi_flavor_set(dip, SCSA_FLAVOR_SMP); } In the future, with SCSAv3, establishing the flavor of a child will be done by SCSA itself. In the implementation of flavor-specific tran functions called by target drivers, flavors can be used to select the correct transport operation vector. sas_hba_tran_t *tran = ndi_flavorv_get(self, SCSA_FLAVOR_SMP); When common SCSA scsi_hba.c code needs to perform different operations based on flavor of an enumerated child: switch (ndi_flavor_get(child) { case XXX: _xxx_(); /* xxx flavor */ break; case YYY: _yyy_(); /* yyy flavor */ break; } With SCSA, the 'vanilla' flavor is associated with scsi_device(9S) child using scsi_hba_tran(9S) transport services. NOTE: For SCSAv3, the ndi_flavor* interfaces will only be used within the common SCSA framework code. There is no intent to make the ndi_flavor* interfaces public as part of the SCSAv3. 4.5 Alternatives: No reasonable alternatives to solve the problem have been found. Since all proposed interfaces are Private, this case is not preventing a future project from implementing more sophisticated ways of plumbing flavor-specific transport services. 4.6 Man Pages These are private interfaces that, like all other ndi_* functions and interfaces defined by [1], have no man pages. 4.7 Release Binding Micro/patch binding is requested. 4.8 References [1] PSARC case that introduced smp transport extensions Serial Attached SCSI (SAS) Management Protocol (SMP) support for Solaris http://sac.sfbay/PSARC/2007/595 http://www.opensolaris.org/os/community/arc/caselog/PSARC/2007/595 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: Automatic 6.6. ARC Exposure: open From carlsonj@phorcys.east.sun.com Fri Feb 13 06:56:42 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 n1DEugTf028583 for ; Fri, 13 Feb 2009 06:56:42 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1DEueo2010480; Fri, 13 Feb 2009 06:56:42 -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 <0KF00045TEUHR000@brm-avmta-1.central.sun.com>; Fri, 13 Feb 2009 07:56:41 -0700 (MST) Received: from phorcys.east.sun.com ([129.148.174.143]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KF000JHPEUG6T60@brm-avmta-1.central.sun.com>; Fri, 13 Feb 2009 07:56:40 -0700 (MST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1DEucIN011010; Fri, 13 Feb 2009 09:56:38 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n1DEucHM011007; Fri, 13 Feb 2009 09:56:38 -0500 (EST) Date: Fri, 13 Feb 2009 09:56:38 -0500 From: James Carlson Subject: Re: ndi flavors [PSARC/2009/102 Self Review] In-reply-to: <200902130114.n1D1EZg8024256@sac.sfbay.sun.com> To: Christopher Horne Cc: PSARC-ext@sun.com, scsav3-eng@sun.com Message-id: <18837.35366.514540.512037@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902130114.n1D1EZg8024256@sac.sfbay.sun.com> Status: RO Content-Length: 1911 Christopher Horne writes: > Associated with each device node is private data that may be > accessed via ddi_[gs]et_private_state(9F). The meaning of that data I can't find such a thing in Solaris, so I'm going to guess that you actually meant ddi_[gs]et_driver_private(9F). Is that right? > The proposal is to allow a nexus driver to declare, at attach time, > how many flavors of children they support and to ask the DDI > framework to create private pointer storage for any flavors beyond > the standard vanilla flavor (which uses the existing > ddi_[gs]et_private_state(9F) private data storage mechanism). This may well be a silly question, but please bear with me, as I'm a little confused by this proposal. In the current system, I believe I would do something like this for flavored children: myp = ddi_get_driver_private(dip); switch (myp->my_flavor) { case MY_FLAVOR_A: { my_flavor_a_t *myap = myp->my_flavptr; ... In other words, a common structure (used with the existing private data area mechanism) plus a discriminated type for the "flavor" part (an enum plus either a void pointer or a union). With this proposed new system, that code seems to become: myp = ddi_get_driver_private(dip); switch (ndi_flavor_get(dip)) { case MY_FLAVOR_A: { my_flavor_a_t *myap = ndi_flavorv_get(dip); ... I'm thus confused about how this is a better solution, and I must be missing something. At most, it seems like I could forgo the initial ddi_get_driver_private call (if I don't need the common data for some reason), but I still get two new calls in exchange. Can you explain what the new solution does that the simpler one doesn't? -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From storycrafter@gmail.com Fri Feb 13 08:45:48 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 n1DGjmtI022163 for ; Fri, 13 Feb 2009 08:45:48 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1DGjfQv006356; Fri, 13 Feb 2009 08:45:47 -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 <0KF000F23JWA7U00@brm-avmta-1.central.sun.com>; Fri, 13 Feb 2009 09:45:46 -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 <0KF000EENJW9RG00@brm-avmta-1.central.sun.com>; Fri, 13 Feb 2009 09:45:46 -0700 (MST) Received: from relay44i.sun.com ([192.5.209.118]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1DGZhQu021387; Fri, 13 Feb 2009 16:45:45 +0000 (GMT) Received: from mms48es.mms.us.syntegra.com ([160.41.221.230] [160.41.221.230]) by relay44i.sun.com with ESMTP id BT-MMP-1419774; Fri, 13 Feb 2009 16:45:45 +0000 (Z) Received: from relay42i.sun.com (relay42i.sun.com [192.5.209.72]) by mms48es.mms.us.syntegra.com with ESMTP id BT-MMP-19795870; Fri, 13 Feb 2009 16:45:45 +0000 (Z) Received: from mail-ew0-f19.google.com ([209.85.219.19] [209.85.219.19]) by relay4i.sun.com with ESMTP id BT-MMP-11521198; Fri, 13 Feb 2009 16:45:45 +0000 (Z) Received: by mail-ew0-f19.google.com with SMTP id 12so1082482ewy.8 for ; Fri, 13 Feb 2009 08:44:54 -0800 (PST) Received: by 10.210.119.16 with SMTP id r16mr1751291ebc.91.1234543494662; Fri, 13 Feb 2009 08:44:54 -0800 (PST) Received: from ?172.16.12.121? ([70.232.181.5]) by mx.google.com with ESMTPS id 28sm411005eyg.55.2009.02.13.08.44.52 (version=TLSv1/SSLv3 cipher=RC4-MD5) ; Fri, 13 Feb 2009 08:44:53 -0800 (PST) Date: Fri, 13 Feb 2009 10:44:50 -0600 From: Mark Martin Subject: Re: ndi flavors [PSARC/2009/102 Self Review] In-reply-to: <200902130114.n1D1EZg8024256@sac.sfbay.sun.com> To: Christopher Horne Cc: PSARC-ext@sun.com, scsav3-eng@sun.com Message-id: <4995A382.5070009@gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=R1k4h/xnyuTfSw+BKBE+QwKQRfNXUufo9aYJT4PsJRM=; b=HMuBlnPQAjpsBotkC4UW/5kOT0IMk9WOTTbHihjNkvoyOdFfxT3yCrMNKUfVb/5m2e 8D92A698wr1XsUtIHdWMumnYZdJBZH3Ug2uqUIJLsGmrVi9GN7Hlb+Te0La734W7veqA w+TVOUkcsU+KUrwo6r4rOxsg31QHkFml1Bgmc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=L4cEImX8axztdHNuzZsDpzVVRenwgXtjj2KTe21gW7yOx/+fTnphJILD10GsBrZrCA SJVQy1IGRIGpO7dQJn6lGJCNGAC8VC1NRcGo1j9G8foo+XtfPnKEptcBYfArQxyQyD+2 r32T0xZ0QiHe/3ZcajqTAMFC0mVmilVHcqWGA= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=-1.1/5.0, scanned in 0.121sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200902130114.n1D1EZg8024256@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) Status: RO Content-Length: 909 Pointless nit follows... Christopher Horne wrote: > I am sponsoring the following fasttrack for Matthew Jacob. Micro/patch > binding is requested. I believe the case qualifies for self review > (since all the interfaces are Consolidation Private) and have filed it > as Closed Approved Automatic. If there is a request, I'd be happy to > convert it to a fasttrack and set the timer to enable further > discussion. > > -Chris > > > 1. Introduction > 1.1. Project/Component Working Name: > ndi flavors > > > 4.8 References > > [1] PSARC case that introduced smp transport extensions > Serial Attached SCSI (SAS) Management Protocol (SMP) support for Solaris > http://sac.sfbay/PSARC/2007/595 > http://www.opensolaris.org/os/community/arc/caselog/PSARC/2007/595 > Should be: http://www.opensolaris.org/os/community/arc/caselog/2007/595/ No (PS|LS|WS|FW)ARC needed in caselog urls. From Chris.Horne@sun.com Tue Feb 17 18:39:33 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 n1I2dXUA006592 for ; Tue, 17 Feb 2009 18:39:33 -0800 (PST) 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 n1I2dXxK023705; Tue, 17 Feb 2009 18:39:33 -0800 (PST) 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 <0KF800M27Q1XET00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 17 Feb 2009 18:39:33 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KF8007H5Q1UC7D0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 17 Feb 2009 18:39:30 -0800 (PST) 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 n1I2dU5I020975; Wed, 18 Feb 2009 02:39:30 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KF800M00PG81U00@mail-amer.sun.com>; Tue, 17 Feb 2009 19:39:30 -0700 (MST) Received: from sun.com ([unknown] [129.150.32.241]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KF800MDCQ19S680@mail-amer.sun.com>; Tue, 17 Feb 2009 19:39:13 -0700 (MST) Date: Tue, 17 Feb 2009 19:39:09 -0700 From: Chris Horne Subject: Re: ndi flavors [PSARC/2009/102 Self Review] In-reply-to: <18837.35366.514540.512037@gargle.gargle.HOWL> Sender: Chris.Horne@sun.com To: James Carlson Cc: Christopher Horne , PSARC-ext@sun.com, scsav3-eng@sun.com Message-id: <499B74CD.7070100@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.4.1.325704 References: <200902130114.n1D1EZg8024256@sac.sfbay.sun.com> <18837.35366.514540.512037@gargle.gargle.HOWL> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20040414 Status: RO Content-Length: 473 In offline communication with James.Carlson@Sun.COM we have closed on this proposal. There was no changes to the interfaces proposed, but the spec has undergone substantial change. In the same offline communication, Jim has agreed to a +1 (contingent on a revised). The updated spec is available here: http://sac.sfbay/PSARC/2009/102/materials/ndi_flavor.fasttrack.txt http://www.opensolaris.org/os/community/arc/caselog/2009/102/ndi_flavor.fasttrack.txt Thanks -Chris From carlsonj@phorcys.east.sun.com Wed Feb 18 04:43:34 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 n1IChYYJ000378 for ; Wed, 18 Feb 2009 04:43:34 -0800 (PST) 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 n1IChWhg002061; Wed, 18 Feb 2009 04:43:33 -0800 (PST) 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 <0KF900K1JI0KPC00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 18 Feb 2009 04:43:32 -0800 (PST) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KF900DSVI0JCD60@nwk-avmta-1.sfbay.Sun.COM>; Wed, 18 Feb 2009 04:43:32 -0800 (PST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1IChPSX021070; Wed, 18 Feb 2009 07:43:25 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n1IChPoS021067; Wed, 18 Feb 2009 07:43:25 -0500 (EST) Date: Wed, 18 Feb 2009 07:43:25 -0500 From: James Carlson Subject: Re: ndi flavors [PSARC/2009/102 Self Review] In-reply-to: <499B74CD.7070100@sun.com> To: Chris Horne Cc: PSARC-ext@sun.com, scsav3-eng@sun.com Message-id: <18844.621.483487.815932@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902130114.n1D1EZg8024256@sac.sfbay.sun.com> <18837.35366.514540.512037@gargle.gargle.HOWL> <499B74CD.7070100@sun.com> Status: RO Content-Length: 772 Chris Horne writes: > In offline communication with James.Carlson@Sun.COM we have > closed on this proposal. There was no changes to the interfaces > proposed, but the spec has undergone substantial change. In > the same offline communication, Jim has agreed to a +1 > (contingent on a revised). > > The updated spec is available here: > http://sac.sfbay/PSARC/2009/102/materials/ndi_flavor.fasttrack.txt > http://www.opensolaris.org/os/community/arc/caselog/2009/102/ndi_flavor.fasttrack.txt That does answer all of the questions I had, so +1. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677