On Mon, 20.12.10 17:26, Fernando Lopez-Lezcano (nando(a)ccrma.Stanford.EDU) wrote:
> In other words, these are setup costs, not maintenance costs.
This may
> cause glitches in a realtime scenario to the extent that clients are
> created and destroyed, but in general I submit that the cost of exec()
> of those new clients is going to dwarf the cost of the inode cache miss
> for the JACK socket. [2]
My experience (caveat: a long time ago, maybe everything has changed
internally in both jack and the kernel and that has invalidated my
experience cache :-) was that using /tmp would lead to constant - not
all the time, but very frequent and not correlated with client
connection/disconnection - xruns (glitches in the audio), using /dev/shm
would fix that immediately. That was why things were moved over to
/dev/shm if I remember correctly.
Smells like something related to atime updating.
Lennart
--
Lennart Poettering - Red Hat, Inc.