On Mon, Apr 06, 2009 at 06:49:25PM +0200, Luca Barbato <[email protected]> wrote: > the result is strange:
what is MPA? the current time? and duration? > the H264 packet with mtime 0.04 is sent before the mpa one with mtime what is mtime here? libev doesn't have n mtime in it's watchers, so it is unclear to me what your problem is. if you are wondering about the order of execution fo the callbacks, then note that this is undefined. if you need a timer to execute before another timer when both become pending at the same time, you need to use priorities. > 0.02 even if it is scheduled before and it's deadline is between the 4th > and the 5th packet same goes for the following ones. It is not at all clear to me what this refers to in terms of libev. Could you make a single example of how two peridiocs were configured, how they were executed, and how that differes from what you expect? On Tue, Apr 07, 2009 at 05:52:43PM +0200, Luca Barbato <[email protected]> wrote: > After digging a bit seems apparent that ev_periodic suffer starvation I don't understand what you mean with starvation here. Can you explain, in libev's terms, how you configure the periodics, and how their execution changes? If you reconfigure some other periodic watcher while one is active, that's legal, but will take effect immediately (without changing it's pending status). > the others starve). I'm using it wrongly, is ev_periodic supposed to > behave this way or is there a bug? My problem is that I have no clue how your periodics behave, from your description (I didn't look at the code). -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / [email protected] -=====/_/_//_/\_,_/ /_/\_\ _______________________________________________ libev mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
