Hi Andrew,

On Mon, Mar 05, 2007 at 04:50:43PM +0000, Andrew Doran wrote:
[snip]

> These should be prefixed as done for existing members of the
> structure, e.g p_sched, l_sched and so on. I think schedstate_percpu
> is probably a better place for any per-CPU data than struct cpu_data
> itself.

Regarding naming: I'd propose cpu_sched_info, p_sched_info and
l_sched_info. Mindaugas is also fine with these.

Regarding where to place cpu_sched_info: Mindaugas and me discussed
about this some time ago and we came to the conclusion that cpu_data
might be more appropriate, since things we'll store there are not
literally scheduler state.

Regards,
Daniel

-- 
Daniel Sieger
Faculty of Technology
Bielefeld University
wwwhomes.uni-bielefeld.de/dsieger