--disable-shm[=BOOL]
PulseAudio clients and the server can exchange audio data via POSIX shared memory segments (on systems
that support this). If disabled PulseAudio will communicate exclusively over sockets. Please note that
data transfer via shared memory segments is always disabled when PulseAudio is running with --system
enabled (see above).
PulseAudio clients and the server can exchange audio data via POSIX shared memory segments (on systems
that support this). If disabled PulseAudio will communicate exclusively over sockets. Please note that
data transfer via shared memory segments is always disabled when PulseAudio is running with --system
enabled (see above).
Edit:
PulseAudio adopts a client/server model that is very similar in principle to that of the X11 system. It is the server that actually outputs the audio and the client app that tells the server what to play. While this approach can be inefficient, resulting in the copying of audio data around, PulseAudio goes to great lengths to ensure that data copying and other latency-prone operations are kept to a minimum. In the common use case of both client and server running on the same machine, PulseAudio uses SHM (Shared Memory) to ensure that data sent from the client to server is not copied across the wire. The core of the PulseAudio server itself is "zero copy" meaning that references to the data are passed around without actually copying the data itself.
Comment