On Mon, 4 May 2015, Jiang Liu wrote:
> +enum {
> + /* Allocate CPU vectors from CPUs on device local node */
> + X86_VECTOR_POL_NODE = 0x1,
> + /* Allocate CPU vectors from all online CPUs */
> + X86_VECTOR_POL_GLOBAL = 0x2,
> + /* Allocate CPU vectors from caller specified CPUs */
> + X86_VECTOR_POL_CALLER = 0x4,
> + X86_VECTOR_POL_MIN = X86_VECTOR_POL_NODE,
> + X86_VECTOR_POL_MAX = X86_VECTOR_POL_CALLER,
> +}
> +static unsigned int vector_alloc_policy = X86_VECTOR_POL_NODE |
> + X86_VECTOR_POL_GLOBAL |
> + X86_VECTOR_POL_CALLER;
> +static int __init apic_parse_vector_policy(char *str)
> +{
> + if (!strncmp(str, "node", 4))
> + vector_alloc_policy |= X86_VECTOR_POL_NODE;
This does not make sense. X86_VECTOR_POL_NODE is already set.
> + else if (!strncmp(str, "global", 6))
> + vector_alloc_policy &= ~X86_VECTOR_POL_NODE;
Why would one disable node aware allocation? We fall back to the
global allocation anyway, if the node aware allocation fails.
I'm completely missing the value of this command line option.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
