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

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Nick Piggin <nickpiggin@...>
Cc: Peter Zijlstra <a.p.zijlstra@...>, Ingo Oeser <ioe-lkml@...>, Paul Jackson <pj@...>, <linux-kernel@...>, Con Kolivas <kernel@...>, Derek L. Fults <dfults@...>, devik <devik@...>, Dimitri Sivanich <sivanich@...>, Dinakar Guniguntala <dino@...>, Emmanuel Pacaud <emmanuel.pacaud@...>, Frederik Deweerdt <deweerdt@...>, Ingo Molnar <mingo@...>, Matthew Dobson <colpatch@...>, Max Krasnyansky <maxk@...>, <rostedt@...>, Oleg Nesterov <oleg@...>, Paul E. McKenney <paulmck@...>, Paul Menage <menage@...>, Randy.Dunlap <rddunlap@...>, <suresh.b.siddha@...>, Thomas Gleixner <tglx@...>
Date: Wednesday, June 4, 2008 - 5:58 am

Nick Piggin wrote:

IMHO,

What is an abonination, is that cpusets are equired for this type of 
isolation to begin with, even on a 2 processor machine.

I would like the option to stay and be extended like Max originally
proposed. If cpusets/hotplug are configured isolation would be obtained 
using them. If not then isolcpus could be used to get the same isolation.

 From a user land point of view, I just want an easy way to fully 
isolate a particular cpu. Even a new syscall or extension to 
sched_setaffinity would make me happy. Cpusets and hotplug don't.

Again this is just MHO.

Regards
Mark

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Inquiry: Should we remove "isolcpus= kernel boot option?..., Mark Hounschell, (Wed Jun 4, 5:58 am)
Re: Inquiry: Should we remove "isolcpus= kernel boot option?..., Michael Trimarchi, (Thu Jun 5, 10:57 am)