On 21 April 2013 15:52, Ján Veselý <[email protected]> wrote: > There are two things to do: > 1) fix fibril creation so that it won't kill the task if there is not > enough memory. This will result in unusable mouse and probably > stuck/ignored keys, but should prevent driver kill. > > 2) add single fibril interrupt handling mode to guarantee serial > handling and hope that the added benefit of better performance is good > enough to remedy your situation. If the performance is still not good, > it will result in unusable mouse and stuck/ignored keys. > > Your setup is a nice test case so implementing 1) first might be a > good idea. I'll try to have a look > on both when I get some time. >
Without some kind of per-task resource limits, 1) will only help as long as no task in the entire system happens to access late-reserved pages. And there is still very little benefit in keeping a task that consumes all memory and cpu to run for no purpose - it will be permanently stuck anyway. 3) Maybe it would be better if the driver itself understood the protocol and was able to combine the moves in-place instead of buffering them needlessly. -- Jirka Z. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
