> From: Horst H. von Brand [mailto:[EMAIL PROTECTED] > That means that there isn't a need for that memory at all (and so they
In the current isolated non-production, not actually bearing a load test case yes. But if I can't get it to not swap on an idle system I have no hope of avoiding OOM on a loaded system. > In any case, how do you know it is the tar data that stays around, and not > just that the number of pages "in use" stays roughly constant? I'm not dumping the contents of memory so I don't. > - What you are doing, step by step Trying to deliver a high availability, linearly scalable, clustered iSCSI storage solution that can be upgraded with minimum downtime. > - What are your exact requirements OOM not to kill anything. > - In what exact way is it missbehaving. Please tell /in detail/ how you OOM kills important stuff. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
