Quote:
Another drawback that tman reminded me of is that this httpd would now be running in userspace, where the greedy player would be starving it by running at realtime priority. The good thing about having khttpd in the kernel is we get good response times. When you're running in userland, the player wins, and everyone else loses. I would imagine a significant negative effect on the responsiveness of the web interface if the httpd moves to user space.


The only scheduler difference between an all-kernelspace thread and one which runs in userspace is that, in userspace, it can be preempted mid-stride, whereas in kernelspace (on these kernels) it is never preempted.

Apart from that, the real-time priority player app still gets scheduled before the webserver, even if it's a kernel based webserver.

I don't think we'll see much of a difference due to the scheduler.

But if we leave it as pageable, then there may be some times when it has to be paged back into memory, and it will be slower whenever that happens. I doubt this will be common, though, and a simple mlockall() "fixes" it for those willing to expend the RAM on it.

Cheers