Messages in this thread |  | | | Date | Thu, 9 Feb 2006 15:10:45 -0600 | | From | Ram Gupta <> | | Subject | RSS Limit implementation issue |
| |
I am working to implement enforcing RSS limits of a process. I am planning to make a check for rss limit when setting up pte. If the limit is crossed I see couple of different ways of handling .
1. Kill the process . In this case there is no swapping problem.
2. Dont kill the process but dont allocate the memory & do yield as we do for init process. Modify the scheduler not to chose the process which has already allocated rss upto its limit. When rss usage fallsbelow its limit then the scheduler may chose it again to run. Here there is a scenario when no page of the process has been freed or swapped out because there were enough free pages? Then we need a way to reschedule the process by forcefully freeing some pages or need to kill the process.
I am looking forward for your comments & pros/cons of both approach & any other alternatives you might come up with.
Thanks Ram Gupta - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |