Re: [PATCH 2/5] cpumask: make task_struct.cpus_allowed acpumask_var_t

From: Christoph Lameter
Date: Fri Jun 25 2010 - 12:05:47 EST

On Fri, 25 Jun 2010, Rusty Russell wrote:

> Even better would be to point to the fixed "one cpu" and "all cpus"
> masks where possible, and make a copy when setting it to something
> else. But you'd have to track down those naughty places which frob it
> directly...

Put it into a read only segment?

What is the estimated performance impact of adding a level of indirection
(and a potential cache miss) to a number of critical code paths?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at