"Justin" == Justin Zygmont <[EMAIL PROTECTED]> writes: Justin> On Tue, 9 Jan 2007, Darren J Moffat wrote: >> Nikolay Piskun wrote: >>> I am trying to implement in C++ something like what I get from: kstat -m >>> cpu_info | grep core_id >> >> That isn't what I was asking. >> >> Once you know the number of cores vs threads vs sockets etc what are you >> planning on doing with the information in your application ? >> >> I very very very strongly advise against any application code making >> scheduling or optimisation or scaling decisions based on this >> information. I guarantee even if you get it correct now the next >> processor will change things for you (no that isn't a prediction on Sun's >> next hardware being different just a fact that for applications this just >> isn't meaningful information). >> >> One type of application where I think it is okay to know this information >> is one giving information about the platform - for example a management >> agent for SNMP or something like that.
Justin> does anyone know of any resources that explains about how Justin> these T1 cpu's operate in everyday use. I think many people Justin> may not fully understand how the threading can be an advantage Justin> or how to make better use of it. Or worse, they *think* they understand it, then try running a workload that can't take advantage of it and complain about the poor performance. One place to start: http://www.sun.com/servers/coolthreads/overview/cooltools.jsp Additionally, potential customers might (probably) want to run cooltst <URL:http://cooltools.sunsource.net/cooltst/> to see if their application is suitable for use with a T1000 or T2000. Is that what you're looking for, or more technical details about how a T1 processor works w.r.t. how threads are scheduled, how cores are shared between threads, etc.? -- Dave Marquardt Sun Microsystems, Inc. Austin, TX +1 512 401-1077 (SUN internal: x64077) _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
