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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Paul Jackson
Date: Tuesday, June 3, 2008 - 5:49 pm

I'll NAQ this one.

As a result of the separate lkml thread:

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

and as a result of there not yet being a good reason -to- remove this,
other than a few kernel developers who don't like it, I conclude that
we should not just remove the "isolcpus=" feature.

It might be that we should deprecate it, as I have suggested in the
past.  But I'm not now seeing even a good reason for that.

-- 
                  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 sch ..., Paul Jackson, (Tue Jun 3, 5:49 pm)