AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
SGI IRIX DrLoser was on of the first to stop using pure sysvinit.Ģ) Did it involve anything like Systemd? Or cgroups? I’m going to make this really, really, really simple for you, oiaohm. There are a lot of things with Linux where the scheduler just cannot get enough information to make the right selections for desktop usage. KDBUS idea also plays into allowing the scheduler to have better information to make selections over cpu time. DRI3 helps a little dma-buf entries in kernel space you can work out what applications have an active rendering window. The scheduler need to be able to find out what applications have active windows and what applications have active audio connections and bias cpu time in to those applications for desktop usage. The reality here for desktop usage we really don’t want a complete fair scheduler. So your example DrLoser of Avid or IRIX is someone using Google who had no clue that IRIX number one was not sysvinit as such and also really was bypassing X11 not working with X11. Also IRIX scheduler could bias cpu time to the dominate application the advantage of only shipping on hardware that video card drivers were not black boxes. By the way the Avid solution on IRIX to the X11 problem was just lock full screen and use OpenGL Direct Rendering to basically bi-pass X11 and write a texture straight to screen.
0 Comments
Read More
Leave a Reply. |