Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 

On 11/7/06, Paul Jackson <[email protected]> wrote:

> > 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)?


Yes.



If you're reluctant to do so, why?


As I said, mainly /proc pollution.

But it's not a big deal, so I can drop it unless there's a strong
argument from others in favour of keeping it.

Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux