2012/7/9 Peter Meerwald <pmeerw at pmeerw.net>: > >> >> 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 :) Ah, you're concerned of embedded devices. Sorry that I haven't thought about it yet. I'm developing on desktop devices. :) So making it configurable seems to be a must. > > hope the patch doesn't get too ugly with tons of #ifdefs My new code doesn't add any #ifdef. They're brought into this patch via the diff tool... -deng
