[pulseaudio-discuss] [PATCH RFCv3 21/51] pstream: Don't call defer_enable() on SHMRELEASE

Peter Meerwald pmeerw at pmeerw.net
Tue Nov 4 15:26:16 PST 2014


From: Peter Meerwald <p.meerwald at bct-electronic.com>

... in order to increase the chance that SHMRELEASE will be combined
with some other message; SHMRELEASE gets into the send queue, but
the mainloop is not notified about it

Signed-off-by: Peter Meerwald <pmeerw at pmeerw.net>
---
 src/pulsecore/pstream.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/pulsecore/pstream.c b/src/pulsecore/pstream.c
index e1b84c6..88bf5d4 100644
--- a/src/pulsecore/pstream.c
+++ b/src/pulsecore/pstream.c
@@ -459,7 +459,11 @@ void pa_pstream_send_release(pa_pstream *p, uint32_t block_id) {
 #endif
 
     pa_queue_push(p->send_queue, item);
-    p->mainloop->defer_enable(p->defer_event, 1);
+    /* Don't call defer_enable() to increase the chance that
+     * the SHMRELEASE item can be combined with some other
+     * item and sent together in one mini buffer.
+     * p->mainloop->defer_enable(p->defer_event, 1);
+     */
 }
 
 /* might be called from thread context */
-- 
1.9.1



More information about the pulseaudio-discuss mailing list