> I hate putting things in the kernel! It's insecure. But what this says is > that for very historical and stupid reasons (related to the ideas of early > timesharing systems like Unix and Multics) folks try to make real-time > algorithms look like ordinary "processes" whose notion of controlling > temporal behavior is abstracted away.
Could you please say more. Why doesn't it work to put the time critical stuff in a separate light weight thread and give it higher priority than the stuff that needs lots of CPU? Is the problem in the scheduler? Is background junk overloading the system? (Are people rebuilding the kernel while video converencing?) Is it too hard to split out the logic that would go in the light weight thread? (get tangled on locks or such) -- These are my opinions. I hate spam. _______________________________________________ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat
