Re: [perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Alexander Kolbasov
Hi Brendan, can I summarize your point as a proposal to extend kstat framework instead of providing filesystem-based representation for CPU-related information? Brendan Gregg - Sun Microsystems <[EMAIL PROTECTED]> wrote: Brendan> G'Day Folks, Brendan> On Mon, Jul 09, 2007 at 02:43:08PM

Re: [perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Alexander Kolbasov
Sherry Moore <[EMAIL PROTECTED]> wrote: >> $ cat /system/cpufs/cpus/0/vendor_string >> $ cat /system/cpufs/cpus/0/l2_cache_size >> >> be sufficient? If the information is available through the CPUfs interface it >> is easy to build wrapper library in any language for accessi

Re: [perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Brendan Gregg - Sun Microsystems
G'Day Folks, On Mon, Jul 09, 2007 at 02:43:08PM -0700, Alexander Kolbasov wrote: > > A related question is what is the best way to get configuration information > > as opposed to performance information. For the kernel, most of the > > performance data is separated out cleanly in kstats, but appli

Re: [perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Eric Saxe
>> On 7/9/07, Alexander Kolbasov <[EMAIL PROTECTED]> wrote: >> >>> Hello, >>> >>> I would like to propose a new "CPUfs" project aimed at providing extended >>> observability for the CPUs in the system and their sharing relationships. >>> The >>> main objective is to provide stable infrastruct

[perf-discuss] (no subject)

2007-07-09 Thread Alexander Kolbasov
>From [EMAIL PROTECTED] Mon Jul 9 13: 59:12 2007 Return-Path: <[EMAIL PROTECTED]> Received: from engmail3mpk.sfbay.Sun.COM (engmail3mpk.SFBay.Sun.COM [129.146.11.26]) by jurassic-x4600.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l69KxC0Z281295 (version=TLSv1/SSLv3 cipher=EDH

Re: [perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Alexander Kolbasov
> I share Brian's view on the possibility of implementing something > similar to Linux's /proc/cpuinfo. During my development days on Linux, > I grew quite fond of the /proc/cpuinfo interface, and found it > extremely extensible to include additional information as they become > available on new C

Re: [perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Alexander Kolbasov
> A related question is what is the best way to get configuration information > as opposed to performance information. For the kernel, most of the > performance data is separated out cleanly in kstats, but applications > still have constructs in /proc such as prusage, which contains the > cpu usa

Re: [perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Brian Gupta
On 7/9/07, Alexander Kolbasov <[EMAIL PROTECTED]> wrote: > On 7/9/07, Alexander Kolbasov <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > I would like to propose a new "CPUfs" project aimed at providing extended > > observability for the CPUs in the system and their sharing relationships. > > T

Re: [perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Alexander Kolbasov
> On 7/9/07, Alexander Kolbasov <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > I would like to propose a new "CPUfs" project aimed at providing extended > > observability for the CPUs in the system and their sharing relationships. > > The > > main objective is to provide stable infrastructure fo

Re: [perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Brian Gupta
On 7/9/07, Alexander Kolbasov <[EMAIL PROTECTED]> wrote: Hello, I would like to propose a new "CPUfs" project aimed at providing extended observability for the CPUs in the system and their sharing relationships. The main objective is to provide stable infrastructure for representing CPU propert

[perf-discuss] [observability-discuss] Project proposal: CPUfs

2007-07-09 Thread Alexander Kolbasov
Hello, I would like to propose a new "CPUfs" project aimed at providing extended observability for the CPUs in the system and their sharing relationships. The main objective is to provide stable infrastructure for representing CPU properties for user-land applications. Currently some CPU-related

Re: [perf-discuss] Memory leaks detection

2007-07-09 Thread Alexander Gorshenev
If it is a FAQ it deserves to be in some Solaris FAQ http://www.genunix.org/wiki/index.php/Category:FAQ This message posted from opensolaris.org ___ perf-discuss mailing list perf-discuss@opensolaris.org