From bart.smaalders@sun.com Mon Feb 12 15:40:46 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l1CNej5N006898 for ; Mon, 12 Feb 2007 15:40:46 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l1CNeUIr024456 for <@sunmail3mpk.sfbay.sun.com:PSARC-EXT@Sun.COM>; Tue, 13 Feb 2007 07:40:44 +0800 (SGT) 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 <0JDD00J07J3T2U00@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Mon, 12 Feb 2007 15:40:41 -0800 (PST) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JDD00D4IJ3SNX40@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Mon, 12 Feb 2007 15:40:40 -0800 (PST) Received: from zion.eng.sun.com (zion.SFBay.Sun.COM [129.146.17.75]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l1CNeeD0016121; Mon, 12 Feb 2007 15:40:40 -0800 (PST) Received: from [129.146.228.109] (cyber [129.146.228.109]) by zion.eng.sun.com (8.13.7+Sun/8.13.7) with ESMTP id l1CNedA9000055; Mon, 12 Feb 2007 15:40:40 -0800 (PST) Date: Mon, 12 Feb 2007 15:40:11 -0800 From: Bart Smaalders Subject: Re: PSARC/2004/402 CPU caps To: PSARC-EXT@sun.com Cc: Alexander Kolbasov Message-id: <45D0FADB.6020901@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 1.5.0.8 (X11/20061204) Status: RO Content-Length: 457 I'm sponsoring this open fast track for Alexander Kolbasov. The desired release binding is patch. It times out next week (Feb 21, 2007). The spec can be found here: http://www.opensolaris.org/os/project/rm/rctls/cpu-caps/caps_psarc/ (When the case has been approved, I'll make sure we have a permanent copy of the spec in the case directory.) = Bart -- Bart Smaalders Solaris Kernel Performance barts@cyber.eng.sun.com http://blogs.sun.com/barts From carlsonj@phorcys.east.sun.com Tue Feb 13 05:27:34 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l1DDRX6r021233 for ; Tue, 13 Feb 2007 05:27:34 -0800 (PST) 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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l1DDRT37014292; Tue, 13 Feb 2007 13:27:31 GMT 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 <0JDE00D0VLDT3G00@nwk-avmta-2.sfbay.sun.com>; Tue, 13 Feb 2007 05:27:29 -0800 (PST) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JDE00HN9LDRSGC0@nwk-avmta-2.sfbay.sun.com>; Tue, 13 Feb 2007 05:27:27 -0800 (PST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l1DDRR96016068; Tue, 13 Feb 2007 08:27:27 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.13.8+Sun/8.13.8/Submit) id l1DDRQiX016065; Tue, 13 Feb 2007 08:27:26 -0500 (EST) Date: Tue, 13 Feb 2007 08:27:26 -0500 From: James Carlson Subject: Re: PSARC/2004/402 CPU caps In-reply-to: <45D0FADB.6020901@Sun.COM> To: Bart Smaalders Cc: PSARC-EXT@sun.com, Alexander Kolbasov Message-id: <17873.48318.93760.491227@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.2.0.264296 References: <45D0FADB.6020901@Sun.COM> Status: RO Content-Length: 1072 Bart Smaalders writes: > I'm sponsoring this open fast track for Alexander Kolbasov. > The desired release binding is patch. It times out next week > (Feb 21, 2007). > > The spec can be found here: > http://www.opensolaris.org/os/project/rm/rctls/cpu-caps/caps_psarc/ I'm confused by 'rctl zone.cpu-cap' versus 'capped-cpu ncpus' in zonecfg. They appear to be specifying the same thing. Why would an administrator need two different ways to specify the same thing? What happens if both are set? It doesn't look to me like 2006/496 has been delivered yet (it's only in snv_56), so there's still time to change things and no need at all to keep compatibility -- if that's the concern. On the 'action' field, the text of the case shows only 'deny' being used. I assume that 'none' and 'signal' are also possible for CPU caps. Is that right? -- James Carlson, Solaris Networking Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Gerald.Jelinek@sun.com Tue Feb 13 08:45:37 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l1DGjaww024880 for ; Tue, 13 Feb 2007 08:45:36 -0800 (PST) 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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l1DGjENm025795; Tue, 13 Feb 2007 16:45:34 GMT 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 <0JDE00805UJXED00@brm-avmta-1.central.sun.com>; Tue, 13 Feb 2007 09:45:33 -0700 (MST) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JDE00K0LUJXUB80@brm-avmta-1.central.sun.com>; Tue, 13 Feb 2007 09:45:33 -0700 (MST) Received: from fe-amer-01.sun.com ([192.18.108.175]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l1DGjXZd021482; Tue, 13 Feb 2007 09:45:33 -0700 (MST) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JDE00701UEXHC00@mail-amer.sun.com> (original mail from Gerald.Jelinek@Sun.COM); Tue, 13 Feb 2007 09:45:33 -0700 (MST) Received: from [192.9.61.89] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JDE00GFDUJVV0M0@mail-amer.sun.com>; Tue, 13 Feb 2007 09:45:32 -0700 (MST) Date: Tue, 13 Feb 2007 09:42:52 -0700 From: Jerry Jelinek Subject: Re: PSARC/2004/402 CPU caps Sender: Gerald.Jelinek@sun.com To: PSARC-EXT@sun.com, james.d.carlson@sun.com Cc: Alexander.Kolbasov@sun.com, bart.smaalders@sun.com, Gerald.Jelinek@sun.com Message-id: <45D1EA8C.1090703@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 1.5.0.8 (X11/20061110) Status: RO Content-Length: 3041 I would like to respond to the following question since the zones team worked with Sasha on this part of his proposal. James Carson wrote: > I'm confused by 'rctl zone.cpu-cap' versus 'capped-cpu ncpus' in > zonecfg. > > They appear to be specifying the same thing. Why would an > administrator need two different ways to specify the same thing? What > happens if both are set? > > It doesn't look to me like 2006/496 has been delivered yet (it's only > in snv_56), so there's still time to change things and no need at all > to keep compatibility -- if that's the concern. These are two different things. We discussed this is in the 2006/496 case but let me try to recap here. This is not a compatibility issue. zone.cpu-cap is a resource control (rctl). The 2006/496 case introduced some new zonecfg resources named 'capped-memory' and 'dedicated-cpu'. Although zonecfg calls these 'resources' these have nothing to do with resources in the rctl sense. They are just a property grouping within zonecfg. As part of 2006/496 we discussed the idea of adding new zonecfg resources to simplify the way that zonecfg can configure resource management. Sasha's proposal is the next step here. We want to add a new zonecfg resource named 'capped-cpu'. Within that resource is one property named 'ncpus'. That property is an rctl alias for the zone.cpu-cap rctl and will configure that rctl, similar to the way that the other rctl aliases work. Again, there are more details in 2006/496. With this new scheme, the simple and preferred way to set up rctls in zonecfg is via these rctl alias. Thus, a user would now 'add capped-cpu' within zonecfg and then set 'ncpus' in order to set up the zone.cpu-cap rctl. The ncpus name is chosen to be consistent with the way we already added the 'dedicated-cpu' resource within zonecfg. We also normalize the units, again to be consistent. Thus, it is possible to set the zone.cpu-cap rctl in two different ways within zonecfg but that is already true for all of the rctls since the introduction of 2006/496 where we added the rctl alias mechanism. Here is the picture of where we are headed with these new zonecfg resources: | dedicated | capped --------------------------------- cpu | temporary | cpu-cap | processor | rctl* | set | --------------------------------- memory | temporary | rcapd, swap | memory | and locked | set* | rctl 2006/496 added 'dedicated-cpu' and 'capped-memory'. This case is proposing to add a 'capped-cpu' resource and eventually we'll add a 'dedicated-memory' resource. Although it may seem silly to have a resource with only a single property in it, we already have other resources in zonecfg that do this and we (the zones team) are starting to think about additional, optional properties that we might want to add under the 'capped-cpu' resource. Please let me know if you have any questions about this or the way I explained it. Thanks, Jerry From carlsonj@phorcys.east.sun.com Tue Feb 13 10:39:50 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l1DIdnc2002594 for ; Tue, 13 Feb 2007 10:39:49 -0800 (PST) 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 l1DIdgDI016651; Wed, 14 Feb 2007 02:39:45 +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 <0JDE00M03ZU64000@nwk-avmta-1.sfbay.Sun.COM>; Tue, 13 Feb 2007 10:39:42 -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 <0JDE00FOKZU6WU90@nwk-avmta-1.sfbay.Sun.COM>; Tue, 13 Feb 2007 10:39:42 -0800 (PST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l1DIdgW9018273; Tue, 13 Feb 2007 13:39:42 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.13.8+Sun/8.13.8/Submit) id l1DIdgIv018270; Tue, 13 Feb 2007 13:39:42 -0500 (EST) Date: Tue, 13 Feb 2007 13:39:41 -0500 From: James Carlson Subject: Re: PSARC/2004/402 CPU caps In-reply-to: <45D1EA8C.1090703@sun.com> To: Jerry Jelinek Cc: PSARC-EXT@sun.com, Alexander.Kolbasov@sun.com, bart.smaalders@sun.com Message-id: <17874.1517.674417.643777@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.2.0.264296 References: <45D1EA8C.1090703@sun.com> Status: RO Content-Length: 1066 Jerry Jelinek writes: > > They appear to be specifying the same thing. Why would an > > administrator need two different ways to specify the same thing? What > > happens if both are set? [...] > These are two different things. We discussed this is in the 2006/496 > case but let me try to recap here. This is not a compatibility issue. [...] > 'ncpus'. That property is an rctl alias for the zone.cpu-cap rctl and will > configure that rctl, similar to the way that the other rctl aliases > work. Again, there are more details in 2006/496. With this new scheme, OK; I think I see it now. If someone sets the rctl to a value that doesn't "map" into the simplified property, then he won't be able to use the simplified version. They are _not_ different things. They're just user-syntactic bits over top of a single (rctl) mechanism. -- James Carlson, Solaris Networking Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Gerald.Jelinek@sun.com Tue Feb 13 10:54:22 2007 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l1DIsMqZ003247 for ; Tue, 13 Feb 2007 10:54:22 -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 l1DIsLp0006343; Tue, 13 Feb 2007 10:54:21 -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 <0JDF00L0B0ILDH00@brm-avmta-1.central.sun.com>; Tue, 13 Feb 2007 11:54:21 -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 <0JDF00E1T0IKYR60@brm-avmta-1.central.sun.com>; Tue, 13 Feb 2007 11:54:20 -0700 (MST) Received: from fe-amer-05.sun.com ([192.18.108.179]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l1DIsIKH018312; Tue, 13 Feb 2007 11:54:20 -0700 (MST) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JDF00A010AQWL00@mail-amer.sun.com> (original mail from Gerald.Jelinek@Sun.COM); Tue, 13 Feb 2007 11:54:19 -0700 (MST) Received: from [192.9.61.89] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JDF006DP0IIC8J1@mail-amer.sun.com>; Tue, 13 Feb 2007 11:54:19 -0700 (MST) Date: Tue, 13 Feb 2007 11:51:39 -0700 From: Jerry Jelinek Subject: Re: PSARC/2004/402 CPU caps In-reply-to: <17874.1517.674417.643777@gargle.gargle.HOWL> Sender: Gerald.Jelinek@sun.com To: James Carlson Cc: PSARC-EXT@sun.com, Alexander.Kolbasov@sun.com, bart.smaalders@sun.com Message-id: <45D208BB.4030209@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <45D1EA8C.1090703@sun.com> <17874.1517.674417.643777@gargle.gargle.HOWL> User-Agent: Thunderbird 1.5.0.8 (X11/20061110) Status: RO Content-Length: 559 James Carlson wrote: > OK; I think I see it now. If someone sets the rctl to a value that > doesn't "map" into the simplified property, then he won't be able to > use the simplified version. > > They are _not_ different things. They're just user-syntactic bits > over top of a single (rctl) mechanism. James, Yes, that is correct. Thats why we chose the term 'rctl alias' to try to describe this. We needed to do it this way for backward compatibility, so there is a compatibility issue, but that came up in 2006/496, not in this case. Thanks, Jerry From akolb@aldan.sfbay.sun.com Tue Feb 13 11:32:14 2007 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l1DJWEMw006169 for ; Tue, 13 Feb 2007 11:32:14 -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 l1DJWAQi017418; Tue, 13 Feb 2007 11:32:13 -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 <0JDF0020929M6V00@brm-avmta-1.central.sun.com>; Tue, 13 Feb 2007 12:32:10 -0700 (MST) Received: from aldan.sfbay.sun.com ([129.146.228.72]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JDF00EG529JYU80@brm-avmta-1.central.sun.com>; Tue, 13 Feb 2007 12:32:07 -0700 (MST) Received: from aldan (localhost [127.0.0.1]) by aldan.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l1DJW7cZ012299; Tue, 13 Feb 2007 11:32:07 -0800 (PST) Date: Tue, 13 Feb 2007 11:32:07 -0800 From: Alexander Kolbasov Subject: Re: PSARC/2004/402 CPU caps In-reply-to: Message from James Carlson "of Tue, 13 Feb 2007 08:27:26 EST." <17873.48318.93760.491227@gargle.gargle.HOWL> To: James Carlson Cc: Bart Smaalders , PSARC-EXT@sun.com, Alexander Kolbasov Message-id: <200702131932.l1DJW7cZ012299@aldan.sfbay.sun.com> MIME-version: 1.0 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 720 > > The spec can be found here: > > http://www.opensolaris.org/os/project/rm/rctls/cpu-caps/caps_psarc/ > > On the 'action' field, the text of the case shows only 'deny' being > used. I assume that 'none' and 'signal' are also possible for CPU > caps. Is that right? No, the 'deny' is the only possible action. As I discussed with RM team it may be possible to introduce 'none' in the future as a way to monitor CPU utilisation without taking any action on it. There is no signal set as a result of a process being delayed due to its cap violation. It is just delayed. The only supported action is 'deny'. - Alex Kolbasov > > -- > James Carlson, Solaris Networking From Menno.Lageman@sun.com Tue Feb 13 11:43:19 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l1DJhI40006638 for ; Tue, 13 Feb 2007 11:43:19 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l1DJhAn3012921; Wed, 14 Feb 2007 03:43:15 +0800 (SGT) 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 <0JDF00E0F2S1BR00@nwk-avmta-2.sfbay.sun.com>; Tue, 13 Feb 2007 11:43:13 -0800 (PST) Received: from gmp-ea-fw-1.sun.com ([129.156.42.6]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JDF009LW2RZM440@nwk-avmta-2.sfbay.sun.com>; Tue, 13 Feb 2007 11:43:12 -0800 (PST) Received: from d1-emea-09.sun.com ([192.18.2.119]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l1DJhBY2022348; Tue, 13 Feb 2007 19:43:11 +0000 (GMT) Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JDF00K012OWHR00@d1-emea-09.sun.com> (original mail from Menno.Lageman@Sun.COM); Tue, 13 Feb 2007 19:43:11 +0000 (GMT) Received: from [192.168.1.125] ([82.168.33.39]) by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JDF003AL2RTUQSE@d1-emea-09.sun.com>; Tue, 13 Feb 2007 19:43:09 +0000 (GMT) Date: Tue, 13 Feb 2007 20:43:05 +0100 From: Menno Lageman Subject: Re: PSARC/2004/402 CPU caps In-reply-to: <45D0FADB.6020901@Sun.COM> Sender: Menno.Lageman@sun.com To: Bart Smaalders Cc: PSARC-EXT@sun.com, Alexander Kolbasov Message-id: <45D214C9.1000104@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <45D0FADB.6020901@Sun.COM> User-Agent: Thunderbird 2.0b1 (X11/20070115) Status: RO Content-Length: 615 Bart Smaalders wrote: > I'm sponsoring this open fast track for Alexander Kolbasov. > The desired release binding is patch. It times out next week > (Feb 21, 2007). > > The spec can be found here: > http://www.opensolaris.org/os/project/rm/rctls/cpu-caps/caps_psarc/ > Is the spec above the most current one? The kstats defined in 5.1 'Zones and Project observability' seem to be missing the 'zonename' kstat. The swap and locked memory kstats from PSARC 2006/598, that are cited as precedents for such kstats, have a zonename kstat. I assume the cpu caps kstats will also have the 'zonename' kstat? Menno From akolb@aldan.sfbay.sun.com Tue Feb 13 11:56:38 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l1DJubqk007611 for ; Tue, 13 Feb 2007 11:56:38 -0800 (PST) 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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l1DJuWsJ017069; Tue, 13 Feb 2007 19:56:35 GMT 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 <0JDF0040J3EAA400@brm-avmta-1.central.sun.com>; Tue, 13 Feb 2007 12:56:34 -0700 (MST) Received: from aldan.sfbay.sun.com ([129.146.228.72]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JDF00EL63EAYOA0@brm-avmta-1.central.sun.com>; Tue, 13 Feb 2007 12:56:34 -0700 (MST) Received: from aldan (localhost [127.0.0.1]) by aldan.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l1DJuXVP012385; Tue, 13 Feb 2007 11:56:33 -0800 (PST) Date: Tue, 13 Feb 2007 11:56:33 -0800 From: Alexander Kolbasov Subject: Re: PSARC/2004/402 CPU caps In-reply-to: Message from Menno Lageman "of Tue, 13 Feb 2007 20:43:05 +0100." <45D214C9.1000104@sun.com> To: Menno Lageman Cc: Bart Smaalders , PSARC-EXT@sun.com, Alexander Kolbasov Message-id: <200702131956.l1DJuXVP012385@aldan.sfbay.sun.com> MIME-version: 1.0 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 782 > Bart Smaalders wrote: > > I'm sponsoring this open fast track for Alexander Kolbasov. > > The desired release binding is patch. It times out next week > > (Feb 21, 2007). > > > > The spec can be found here: > > http://www.opensolaris.org/os/project/rm/rctls/cpu-caps/caps_psarc/ > > > > Is the spec above the most current one? The kstats defined in 5.1 'Zones > and Project observability' seem to be missing the 'zonename' kstat. The > swap and locked memory kstats from PSARC 2006/598, that are cited as > precedents for such kstats, have a zonename kstat. I assume the cpu caps > kstats will also have the 'zonename' kstat? Yes, the zonename variable is present in CPU Caps kstats which will make it consistent with other resource management kstats. - Alex Kolbasov