Le mardi 22 août 2006 à 18:26 +0200, Denis Vlasenko a écrit :
> > I think the problem is also due to mplayer's faulty design. It should
> > be multithreaded and use RT threads for the time sensitive work, like
> > all professional AV applications and many other consumer players do.
>
> RT - yes, multithreaded - unsure. Witness how squid manages to
> serve hundreds of simultaneous streams using just a single process.
>
> Multithreading seems cool on the first glance and it is easier to code
> than clever O_NONBLOCK/select/poll/etc stuff. However,
> on single-CPU boxes, which are still a majority, multithreading
> just incurs context switching penalty. It cannot magically
> make CPU do more work in a unit of time.
The problem with mplayer is latency more than throughput, and for that
multithreading is king. Squid can get away with a 100ms delay between
two packets, mplayer can't.
Xav
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
