Andrew wrote (of exporting cpuset symbols)
> We normally would do this when such modules are merged. Do tell us more..
It was an oversight not to do this when cpusets went in last year,
but we didn't notice, as the loadable module we cared about had a
hack in place from earlier development that avoided needing this.
In cleaning this up, we realized that the module needed to access
task->cpuset->cpus_allowed, and that the correct (and safe) way to
do this, via cpuset_cpus_allowed(), was not available to the module.
The other 4 exports I added on general principles, but don't have
any pressing need for. The one I need is cpuset_cpus_allowed().
The loadable module in question we call 'dplace', and is used to
provide fancier cpuset-relative task placement by manipulating
task->cpus_allowed at exec.
--
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]
