Hi Christophe, any recent kernel will only accept values > -17 for oom_adj. So writing '-17' into oom_adj will only lead to an error, not to the desired behaviour. Patch is attached. Cheers, Hannes -- Dr. Hannes Reinecke hare@xxxxxxx SuSE Linux Products GmbH S390 & zSeries Maxfeldstraße 5 +49 911 74053 688 90409 Nürnberg http://www.suse.de
[multipathd] set oom_adj to a valid value As of 2.6.14, the kernel will only accept oom_adj values of > -17. Writing '-17' into oom_adj will be ignored. This patch fixes the value to -16. Signed-off-by: Hannes Reinecke <hare@xxxxxxx> diff --git a/multipathd/main.c b/multipathd/main.c --- a/multipathd/main.c +++ b/multipathd/main.c @@ -1554,7 +1554,7 @@ child (void * param) } signal_init(); setscheduler(); - set_oom_adj(-17); + set_oom_adj(-16); vecs = gvecs = init_vecs(); if (!vecs)
-- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
