Re: [git pull for -mm] CPU isolation extensions (updated2)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Max Krasnyansky <maxk@...>
Cc: David Miller <davem@...>, <akpm@...>, <torvalds@...>, <linux-kernel@...>, <mingo@...>, <pj@...>, <a.p.zijlstra@...>, <gregkh@...>, <rusty@...>
Date: Wednesday, February 13, 2008 - 2:22 am

On Wednesday 13 February 2008 17:06, Max Krasnyansky wrote:


Hmm, maybe. Removing all sources of latency from the CPU kind of
implies that you have to audit the whole kernel for source of
latency.


OK, but you then are very restricted in what you can do, and easily
can break it especially if you run any userspace on that CPU. If
you just run a kernel module that, after setup, doesn't use any
other kernel resources except interrupt handling, then you might be
OK (depending on whether even interrupt handling can run into
contended locks)...

If you started doing very much more, then you can easily run into
trouble.
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[git pull for -mm] CPU isolation extensions (updated2), Max Krasnyansky, (Tue Feb 12, 12:10 am)
Re: [git pull for -mm] CPU isolation extensions (updated2), Peter Zijlstra, (Tue Feb 12, 2:59 pm)
Re: [git pull for -mm] CPU isolation extensions (updated2), Steven Rostedt, (Wed Feb 13, 1:19 am)
Re: [git pull for -mm] CPU isolation extensions (updated2), Max Krasnyansky, (Wed Feb 13, 1:47 am)
Re: [git pull for -mm] CPU isolation extensions (updated2), Max Krasnyansky, (Tue Feb 12, 11:59 pm)
Re: [git pull for -mm] CPU isolation extensions (updated2), Max Krasnyansky, (Tue Feb 12, 11:32 pm)
Re: [git pull for -mm] CPU isolation extensions (updated2), Max Krasnyansky, (Wed Feb 13, 2:06 am)
Re: [git pull for -mm] CPU isolation extensions (updated2), Nick Piggin, (Wed Feb 13, 2:22 am)
Re: [git pull for -mm] CPU isolation extensions (updated2), Max Krasnyansky, (Wed Feb 13, 1:11 pm)