Matthew Dillon wrote:
As part of the 48-core support some significant scheduler changes
have gone into master, so again HEADS UP there may be some instability.
How do these scheduler changes relate to say, userland preemption or
things of that nature (thinking soft-realtime,
:How do these scheduler changes relate to say, userland preemption or
:things of that nature (thinking soft-realtime, scheduling priority, etc) ?
:
:I know in the past in general you've said thats not really a design goal
:- but, anyhow, seems to relate based on the commit messages
:
:cheers
:
As part of the 48-core support some significant scheduler changes
have gone into master, so again HEADS UP there may be some instability.
The new scheduler changes how contended tokens are dealt with.
Instead of just randomly spinning trying to acquire the token the LWKT
Over the next few days I will be committing work to support systems
with large numbers of cpu memory. The commit made today does not
represent stable support yet and it is also possible that the work may
temporarily destabilize other configurations.
Support for up to 63 cpus
