Re: Core Topology

On 2009-03-24 at 02:54:51 [+0100], Rene Gollent <[email protected]> wrote:
> On Mon, Mar 23, 2009 at 8:01 PM, Ingo Weinhold <[email protected]> wrote:
> > No idea. I guess Axel and Michael would know, but maybe they are a little
> > short on time ATM. At any rate reading the documentation and the 
> > respective
> > source code will definitely help, too. :-)
> 
> Will see what I can do :) On a related note, would anyone be opposed
> to be me extending the kernel struct thread a bit? I'd like to be able
> to track how much of its quantum a thread used for its past few runs,
> since otherwise we don't have any good way (that I can see) to know
> how much of a CPU hog a particular thread was, and for obvious reasons
> I'd like to avoid having to do any dynamic memory allocation in the
> scheduler itself, which leaves me somewhat short on options for places
> to track per-thread data.

I'd say best introduce a scheduler_thread_data* field -- with the 
scheduler_thread_data structure being scheduler implementation private -- 
that is initialized/uninitialized via scheduler hooks on thread 
creation/deletion. This way each scheduler implementation can associate the 
data it needs with the thread. If you want to associate data with teams as 
well, it can be done analogously.

CU, Ingo

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com