PATCH: Root reservations for strict overcommit
This was on my TODO list for a while and it turns out someone already fixed the armwaving overcommit mode for the same problem. It is easy to get into a situation where you have no overcommit and nothing can be done because there is no memory to clean up the stable but non-useful state of the machine.
The fix is trivial and duplicated from the armwaving overcommit code path. The last 3% of the memory can be claimed by root processes only. It isn't a cure but it does seem to solve the real world problems - at least providing you have enough memory for 3% to be useful 8).
commoncap.c renamed from commoncap.c~ +5 -0
@@ -357,6 +357,11 @@ allowed = (totalram_pages -hugetlb_total_pages ()) * sysctl_overcommit_ratio /100 ; +/* +* Leave the last 3% for root +*/ +if (!capable (CAP_SYS_ADMIN )) + allowed -= allowed /32 ; allowed += total_swap_pages;if (atomic_read (&vm_committed_space) < allowed)
Quoted 14 lines · Alan Cox
This was on my TODO list for a while and it turns out someone already fixed the armwaving overcommit mode for the same problem. It is easy to get into a situation where you have no overcommit and nothing can be done because there is no memory to clean up the stable but non-useful state of the machine.
The fix is trivial and duplicated from the armwaving overcommit code path. The last 3% of the memory can be claimed by root processes only. It isn't a cure but it does seem to solve the real world problems - at least providing you have enough memory for 3% to be useful 8).
commoncap.c renamed from commoncap.c~ +0
-0@@ -357,6 +357,11 @@
commoncap.c line 367
Quoted 10 lines
commoncap.c renamed from commoncap.c~ +5
-0allowed = (totalram_pages -hugetlb_total_pages ()) * sysctl_overcommit_ratio /100 ; +/* +* Leave the last 3% for root +*/ +if (!capable (CAP_SYS_ADMIN )) + allowed -= allowed /32 ; allowed += total_swap_pages;if (atomic_read (&vm_committed_space) < allowed)
Would it be a problem to put a lower bound on how much to leave for root? If it's really too small to be useful, perhaps one of (a) reserve enough to be useful or (b) don't bother to reserve at all, should be selected.
I don't know what you have in mind for "useful," but it seems likely that a really small machine would be better off giving up any memory unless it was useful.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
Quoted 3 lines · Bill Davidsen
Would it be a problem to put a lower bound on how much to leave for root? If it's really too small to be useful, perhaps one of (a) reserve enough to be useful or (b) don't bother to reserve at all, should be
Possibly. I'm currently following what someone appears to have decided is correct behaviour. It probably should be tunable
Quoted 7 lines · Alan Cox
Quoted 3 lines · Bill Davidsen
Would it be a problem to put a lower bound on how much to leave for root? If it's really too small to be useful, perhaps one of (a) reserve enough to be useful or (b) don't bother to reserve at all, should be
Possibly. I'm currently following what someone appears to have decided is correct behaviour. It probably should be tunable
I believe it makes more sense to describe it as KB instead of %. Noone should have to reserve 120MB for root on a 4G box. Even if it is tunable, memory size seems better than percent since you'll not have to change it when you add/remove memory from your box.
<<V13>>
Quoted 1 line
Noone should have to reserve 120MB for root on a 4G box.
Much less 120GB on a 4T box ;)
Signature · 3 lines
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.650.933.1373