On Mon, Feb 09, 2004 at 07:32:35PM -0500, Paul Davis
wrote:
its a basic problem with real time software, the
POSIX API etc.
JACK tries to lock *all* the process memory.
This is to ensure that nothing gets swapped out, right ?
Else it is very hard to ensure real time performance ?
(sorry for being somewhat ignorant in this matter).
well, swapping is one aspect. page faults are the other. either way,
yes, we need to ensure that real-time code is never stalled waiting
for data to be bought into memory from disk storage.
Would you consider implementing a work around (aka non
portable kludgery)
a waste of time ?
Mostly, though there are people who would probably find it valuable.
--p