On 12-10-15, 12:31, Saravana Kannan wrote:
Can we use the first CPU in the related CPUs mask? Instead of the first CPU that the policy got created on? The policyX numbering would be a bit more consistent that way.
Okay..
Suggested-by: ?
Will add. Though me/Rafael thought about it long back, but then dropped the idea :)
Didn't notice when this got added. Do we really need this anymore if we don't care about moving the directory and creating symlinks? I don't think we need it anymore. And if we really need to know related - offline, we can use for_each_cpu_and(related, online/present mask)
Its about tracking present-cpus, for which the link is present. So, it is still required.