On Tue, Jun 17, 2008 at 02:04:43PM -0400, Alexander Strange wrote: > > On Jun 17, 2008, at 12:18 PM, Reimar Döffinger wrote: > > > On Mon, Jun 16, 2008 at 07:57:05PM -0400, Alexander Strange wrote: > >> > >> Use it to simplify USE_* macros. > >> FF_THREAD_AUTO needs to be handled better - even if a codec can > >> handle frame-threads, we still don't want to use them if there are > >> enough slices available. > > > > I also do not really like that this design does not allow to use both. > > E.g. when 16 core CPUs become common just one type may not be good > > enough ;-) > > Or to say it differently: I think the problem is not just with > > FF_THREAD_AUTO but in the design in general. > > You can't run out of threads for multiframes, but eventually I guess > it would be better to have x frame threads * x slice threads. Sounds > more useful for encoding, though; does anyone really need to decode > that fast?
You can easily run out of memory or cache though, especially if you try some kind of direct rendering where all frames must fit into a DMA-enable memory range or similar. Greetings, Reimar Döffinger _______________________________________________ FFmpeg-soc mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-soc
