Re: [RFC PATCH 5/8] sched: introduce common topology level initfunction

[Peter Zijlstra]

> +/*
> + * SD_flags allowed in topology descriptions.
> + *
> + * SD_SHARE_CPUPOWER      - describes SMT topologies
> + * SD_SHARE_PKG_RESOURCES - describes shared caches
> + * SD_NUMA                - describes NUMA topologies
> + *
> + * Odd one out:
> + * SD_ASYM_PACKING        - describes SMT quirks
> + *
> + * SD_PREFER_SIBLING      - describes preference for sibling domain
> + */
> +#define TOPOLOGY_SD_FLAGS         \
> +	(SD_SHARE_CPUPOWER |      \
> +	 SD_SHARE_PKG_RESOURCES | \
> +	 SD_NUMA |                \
> +	 SD_ASYM_PACKING |        \
> +	 SD_PREFER_SIBLING)

See SD_PREFER_SIBLING is behavioural, the exact kinda thing we want to
keep out of this mask,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/