Re: [vdr] [PATCH] dynamically sized ringbuffers v2

2007-05-11 Thread Artur Skawina
Klaus Schmidinger wrote: If this auto sized ringbuffers change (which, from what I can see so far - haven't tried it myself - looks like a good idea) is ever to make its way into the official VDR source, you'll need to get rid of the above waiting. It says in receiver.h: ...the call must

Re: [vdr] [PATCH] dynamically sized ringbuffers v2

2007-05-10 Thread Jouni Karvo
Stone writes: It still wouldn't surprise me if this version caused a few overflows, but hopefully these will be very rare. I'm curious how streamdev will function with these buffer changes. And since I am not convinced that this memory footprint issue is significant, I am concerned

Re: [vdr] [PATCH] dynamically sized ringbuffers v2

2007-05-10 Thread clemens kirchgatterer
And since I am not convinced that this memory footprint issue is significant, at a first glance, IMHO dynamic buffers are a good thing. we can get rid of small upper buffer size bounderies all together without wasting amounts of memory. this should result in even less buffer overflows when

Re: [vdr] [PATCH] dynamically sized ringbuffers v2

2007-05-10 Thread Artur Skawina
Stone wrote: It still wouldn't surprise me if this version caused a few overflows, but hopefully these will be very rare. I'm curious how streamdev will function with these buffer changes. it works fine -- i'm using a headless vdr server and streamdev+softdevice clients, so this

Re: [vdr] [PATCH] dynamically sized ringbuffers v2

2007-05-10 Thread Artur Skawina
Jouni Karvo wrote: Stone writes: It still wouldn't surprise me if this version caused a few overflows, but hopefully these will be very rare. I'm curious how streamdev will function with these buffer changes. And since I am not convinced that this memory footprint issue is