Messages in this thread | | | Date | Tue, 7 Nov 2006 11:58:23 -0800 | From | Paul Jackson <> | Subject | Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices |
| |
> > So why is this CONFIG_* option separate? When would I ever not > > want it? > > If you weren't bothered about having the legacy semantics.
You mean if I wasn't bothered about -not- having the legacy semantics?
Let me put this another way - could you drop the CONFIG_CPUSETS_LEGACY_API option, and make whatever is needed to preserve the current cpuset API always present (if CPUSETS themselves are configured, of course)?
If you're reluctant to do so, why?
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.925.600.0401 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |