From Sebastien.Roy@sun.com Fri Feb 26 12:04:26 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 o1QK4QCE017986 for ; Fri, 26 Feb 2010 12:04:26 -0800 (PST) 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.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o1QK4GOA000177 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Fri, 26 Feb 2010 12:04:25 -0800 (PST) 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 <0KYG00B1ZT3AN500@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 26 Feb 2010 12:04:22 -0800 (PST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KYG000VTT3AVTB0@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 26 Feb 2010 12:04:22 -0800 (PST) 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 o1QK4L8e029300 for ; Fri, 26 Feb 2010 20:04:21 +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 <0KYG00800SN1J800@mail-amer.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 26 Feb 2010 13:04:21 -0700 (MST) Received: from [192.168.1.3] ([unknown] [173.76.16.34]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KYG00MQBT35VD10@mail-amer.sun.com>; Fri, 26 Feb 2010 13:04:18 -0700 (MST) Date: Fri, 26 Feb 2010 15:04:16 -0500 From: Sebastien Roy Subject: Crossbow resource usage updates [PSARC/2010/074 FastTrack timeout 03/05/2010] Sender: Sebastien.Roy@sun.com To: psarc-ext@sun.com Cc: venugopal iyer Message-id: <4B882940.6000409@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 User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.7) Gecko/20100131 Lightning/1.0b1 Thunderbird/3.0.1 Status: RO Content-Length: 4158 I'm submitting this fast-track for Venugopal Iyer. The release binding is Patch, but this case depends on the following other cases: PSARC/2009/364 dlstat and flowstat PSARC/2009/448 pool dladm link property PSARC/2009/501 Dynamic Ring Grouping on NICs This case makes modifications to the above cases which have not yet integrated (in other words, there are no incompatible changes introduced due to the fact that these cases will all be integrated simultaneously). All new command-line options are Committed, and link properties introduced are Uncommitted. Updated man pages and man page diffs for dladm(1M), dlstat(1M), and flowstat(1M) are available in the case directory under "materials". Update to PSARC/2009/501 ------------------------ The values for rxrings and txrings properties are changed to support NICs such as bge and ixgbe for which we cannot explicitly specify the number of rings. Thus, the proposed values for rxrings and txrings properties are: sw : This link does not need any hardware rings of the specified type (RX or TX) hw : This link needs at least 1 hardware ring of the specified type (RX or TX) x > 0 : This link needs x rings of the specified type (RX or TX). Additionally, in order to keep the names of the properties consistent and easier to understand, the read-only properties are changed to: rxrings-available: The total number of RX rings available for use, i.e. not exclusively given to any MAC client. txrings-available: The total number of TX rings available for use. rxhwclnt-available: The total number of additional RX hardware-based MAC clients that can be created. Each of these hardware-based MAC client could have one or more RX rings assigned to them. txhwclnt-available: The total number of additional TX hardware-based MAC clients that can be created. Each of these hardware-based MAC clients could have one or more TX rings assigned to them. The value for rxrings or txrings could be set to "sw" or "hw" based on the values of the read-only properties rxhwclnt-available or txhwclnt-available for the underlying device. Further, the read-only property rxrings-available or txrings-available, if not zero, indicates the number of rings that can be assigned to the rxrings and txrings properties. E.g if rxhwclnt-available is 0, then only "sw" links can be created, if not, it specifies the number of "hw" links that can be created. If a link is created as "hw", then the actual number of rings that gets assigned to the link depends on the underlying NIC. If it is ixgbe or bge, then the number of rings assigned to the link is determined from parameters defined at attach time of the device (e.g. via driver.conf). Some NICs like nxge allows users to specify the number of rings required for a link. Thus, a link created with "hw" is given one hardware ring by default. If the link needs more rings, then it can be specified in the rxrings or txrings property. The number of rings available can be obtained from the read-only properties rxhwclnt-available or txhwclnt-available. In order to display the actual number of rings that gets assigned to a link created with "hw", we introduce two read-only properties - rxrings-effective and txrings-effective. Update to PSARC/2009/364 ------------------------ New option is added to dlstat(1m) and flowstat [-a | -A] to display all statistics. Additionally, the examples in the man page are modified (from the ones in the original PSARC case documents). Additionally, we also replace the b and B specifier for -u option with R (Raw) since bits (b) and Bytes (B) is not very meaningful for packet counts. Update to PSARC/2009/448 ------------------------ Adding read-only properties for effective pool and cpus. The existing 'cpus' and new 'pool' data link properties indicate the administrator's intent but are only effective when the datapath is setup and for 'pool', when pools are enabled. The 'cpus-effective' and 'pools-effective' read-only properties will show which cpus and pools are being used for the link. From gdamore@sun.com Fri Mar 5 19:17:32 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 o263HWUf002823 for ; Fri, 5 Mar 2010 19:17:32 -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 o263HWuk017882 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 5 Mar 2010 19:17:32 -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 <0KYU00B07BT8R400@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 05 Mar 2010 20:17:32 -0700 (MST) 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 <0KYU005ENBT7MY20@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 05 Mar 2010 20:17:31 -0700 (MST) 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 o263HVbX014763 for ; Fri, 05 Mar 2010 19:17:31 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KYU00B00BSRES00@fe-sfbay-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 05 Mar 2010 19:17:31 -0800 (PST) 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.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KYU00KIABT75K50@fe-sfbay-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 05 Mar 2010 19:17:31 -0800 (PST) Date: Fri, 05 Mar 2010 19:17:31 -0800 From: "Garrett D'Amore" Subject: PSARC 2010/074 Crossbow resource usage updates Sender: Garrett.Damore@sun.com To: PSARC-ext Message-id: <4B91C94B.2020008@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 User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.5) Gecko/20100117 Lightning/1.0b1 Thunderbird/3.0 Status: RO Content-Length: 112 I've finally reviewed the materials, and they look reasonable to me. +1. Sorry for the delay. - Garrett From Sebastien.Roy@Sun.COM Sat Mar 6 17:50:39 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 o271odhp005892 for ; Sat, 6 Mar 2010 17:50:39 -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 o271odN5007008 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Sat, 6 Mar 2010 17:50:39 -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 <0KYW008012GFCF00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 06 Mar 2010 18:50:39 -0700 (MST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KYW00IUX2GENHB0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 06 Mar 2010 18:50:38 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o271oc10016549 for ; Sun, 07 Mar 2010 01:50:38 +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 <0KYW00B002BZ6Q00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 06 Mar 2010 18:50:38 -0700 (MST) Received: from [192.168.1.3] ([unknown] [173.76.16.34]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KYW002TP2GDQA20@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 06 Mar 2010 18:50:38 -0700 (MST) Date: Sat, 06 Mar 2010 20:50:37 -0500 From: Sebastien Roy Subject: Re: PSARC 2010/074 Crossbow resource usage updates In-reply-to: <4B91C94B.2020008@sun.com> Sender: Sebastien.Roy@Sun.COM To: "Garrett D'Amore" Cc: PSARC-ext Message-id: <4B93066D.3040400@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: <4B91C94B.2020008@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.7) Gecko/20100131 Lightning/1.0b1 Thunderbird/3.0.1 Status: RO Content-Length: 191 On 03/ 5/10 10:17 PM, Garrett D'Amore wrote: > I've finally reviewed the materials, and they look reasonable to me. +1. > The timer having expired, this case is now approved. Thanks, -Seb