* Peter Zijlstra [off-list ref] wrote:
On Fri, May 08, 2015 at 01:58:45PM -0400, Chris Metcalf wrote:
quoted
This prctl() flag for PR_SET_DATAPLANE sets a mode that requires the
kernel to quiesce any pending timer interrupts prior to returning
to userspace. When running with this mode set, sys calls (and page
faults, etc.) can be inordinately slow. However, user applications
that want to guarantee that no unexpected interrupts will occur
(even if they call into the kernel) can set this flag to guarantee
that semantics.
Currently people hot-unplug and hot-plug the CPU to do this.
Obviously that's a wee bit horrible :-)
Not sure if a prctl like this is any better though. This is a CPU
properly not a process one.
So if then a prctl() (or other system call) could be a shortcut to:
- move the task to an isolated CPU
- make sure there _is_ such an isolated domain available
I.e. have some programmatic, kernel provided way for an application to
be sure it's running in the right environment. Relying on random
administration flags here and there won't cut it.
Thanks,
Ingo