Christoph Lameter wrote:
On Fri, 28 Aug 2009, Thomas Gleixner wrote:
What slab queue stuff is running on timers and cannot be switched off
in such a context?
slab does run a timer every 2 second to age queues. If there was activity
then there can be a relatively long time in which we periodically throw
out portions of the cached data.
OK, you have me fully confused now.
From other HPC people, I know the "no noise in my math application"
requirement. But that means the user code that is running on the
CPU must not do anything that wakes the kernel. Not even page faults,
so they pin the memory at job start.
Anything the user code does that needs kernel statistics or
kernel action is "I must fix my user code", or "I accept that
the noise is necessary".
So we don't need to offload stats to other CPUs, stats are not needed.
Device specific stuff should not happen on such a CPU when there is no
device handled on it.
The device may periodically check for conditions that require action.
Again, what is this device and why is it controlled directly by
user-space code. Devices should be controlled even in an HPC
environment by the kernel. AFAIK HPC wants the kernel to be the
bootstrap and data transfer manager running on a small subset of
the total CPUs, with the dedicated CPUs running math jobs.
jim
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
