Re: current->need_reshed, can it be a global flag ?

[george anzinger]

Parity Error wrote:
> 
> instead of need_reshed being a per-task flag, could it be
> as a global flag ?, since every time current->need_reshed
> is checked, schedule() is just called to pick another
> process.
> 
> ---
But for which cpu?  Really this is a short cut to provide a per cpu area
that I think works very well, thank you.

Putting it in a real cpu data area would make access slower.  The
"current" pointer is either very quickly computed or pre loaded in a
register (depends on the platform) so it is about as fast as it can get
as it is.

Also, the flag is often checked by selective preemption code in the
kernel.  Even more often by the full preemption patch.

Nuf said
George