> in any case i'd like to see the externally visible API get in foremost -
> and there now seems to be agreement about that. (yay!) Any internal
> shaping of APIs can be done flexibly between cpusets and the scheduler.
Yup - though Nick and I will have to agree to -some- internal interface
between the cpuset and sched code, at least for the moment.
At least, if we thrash about on this, we won't be changing the externally
visible API around. We'll just continue driving Andrew nuts, not our
users - that's an improvement.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
