On Mon, 2012-07-09 at 17:56 +0200, Peter Meerwald wrote: > > >> The usage model for this ring buffer is that we can peek into what's going on > > >> under the hood without restarting pulseaudio daemon, we enable this via logging > > >> all level's messages. > > > > > > what is the expected memory usage? 512*200 bytes + 200 timestamps? is this > > > per thread? > > > > > > can this be made compile-time configurable? > > > Thanks for your interests in this usage. Yes. It's per thread and the > > memory usage is quite low right now. It's a good idea to make it > > compile time configurable. I'll add that support. :) > > 100KB times ?? threads... there are probably better ways to waste memory > on an embedded device :) > > hope the patch doesn't get too ugly with tons of #ifdefs The usage that I envisage for this it's always enabled except on embedded/production/resource-constrained systems where it would be disabled by configuration. _All_ logging unconditionally goes into the ringbuffer. So if something goes wrong, you don't have to restart PA for verbose logging and wait for things to break again. -- Arun
