[multipathd] correct oom_adj value

[multipathd] correct oom_adj value

[Hannes Reinecke]

[-- Attachment #1: Type: text/plain, Size: 372 bytes --]

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@suse.de
SuSE Linux Products GmbH		S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de

[-- Attachment #2: multipath-tools-oom-adj.patch --]
[-- Type: text/x-patch, Size: 503 bytes --]

[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@suse.de>

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)

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]

Re: [multipathd] correct oom_adj value

[Christophe Varoqui]

On mer, 2005-12-07 at 15:57 +0100, Hannes Reinecke wrote:
> 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.
> 
Applied, thanks.