![]() | |||||||||||
Messages in this thread |
On Tue, 2005-01-11 at 11:20 +0200, Edjard Souza Mota wrote: > > You are definitely curing the symptom instead of the cause. > > > > > 1) ranking for the most likely culprits only starts when memory consumption > > > gets close to the red zone (for example 98% or something like that). We do the ranking only in the oom situation, so what's your point ? > > > 2) killing just gets the first candidate from the list and kills it. > > > No need to calculate > > > at kernel level. So I need a userspace change in order to solve a kernel problem ? > > What is the default behaviour when no userspace settings are available - > > Nothing ? Are you really expecting that we change every root fs in order > > to be able to upgrade the kernel for solving this _kernel_ problem ? > > No, I certainly don't. But, have seen the application we also posted? It is > a test for while, that actually starts a deamon when you boot the kernel > and does rate this application, i.e. an application with root rating priority > so it will never be killed and never lack space for itself. > So, the answer to your 2nd very good point. You did not answer my question at all. I do not want to update my rootfs to solve a problem which exists in the kernel and must be solved in the kernel. tglx - 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/ | ||||||||||
| Last update: 2005-03-22 14:09 [from the cache] ©2003-2008 | |||||||||||