9 Feb
2011
9 Feb
'11
1:53 p.m.
On Wed, Feb 09, 2011 at 06:56:19AM -0500, Paul Davis wrote:
On Wed, Feb 9, 2011 at 3:37 AM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
you should check the jack README... iirc it still talks about this /tmp
stuff.
On 02/08/2011 11:45 PM, Paul Davis wrote:
programs that use the filesystem from a realtime audio thread are
incorrectly written.
a system that allows disk i/o to interfere with a realtime audio
thread is badly configured.
ergo, i would conclude that the only realtime audio programs that can
benefit from this sort of thing are either badly written or running on
a misconfigured system.
JACK itself isn't doing any file I/O - it just happens to use an
inter-process communication system that uses identifiers that are
related to the filesystem. no, but putting JACK's tmpdir on a tmpfs
filesystem does.
current versions of JACK use /dev/shm as the location for this, no
/tmp (this was done years ago).
--p
Thanks for the reply Paul. But what about other applications that use
/tmp? Could they benefit from a /tmp directory mounted on a tmpfs
filesystem? _______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
torben Hohn