Re: [PATCH] sched: Give cpusets exclusive control over sched domains (ie remove cpu_isolated_map)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Max Krasnyansky <maxk@...>
Cc: <mingo@...>, <a.p.zijlstra@...>, <linux-kernel@...>, <menage@...>, <rostedt@...>
Date: Sunday, June 1, 2008 - 10:35 pm

Max K wrote:

I wasn't looking for a variant implementation.  Unless this variant
serves some critical purpose that isolcpus can't provide, I would be
against it.  I'm trying to minimize API changes to kernel users.

I am trying to discuss the reasons for or against removing isolcpus.

I just started a separate lkml thread, with a wider audience, to
address this question:

  Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime uses)

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.940.382.4214
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] sched: Give cpusets exclusive control over sched..., Paul Jackson, (Sun Jun 1, 10:35 pm)