Difference in kmtune and SAM kernel parameters output

[Bob Ballou]

RP7410 running 11i. SAM shows kernel parameter maxuprc=4098 set using formula (NPROC+2). kmtune -l -q maxuprcs
Parameter: maxuprc
Current: 75
Planned: (NPROC+2)
Default: 75
Minimum: -
Module: -
Version: -
Dynamic: Yes

What causes the difference and which value should we believe.

[twang]

what is output from "kmtune -l -q nproc"?

[Bob Ballou]

kmtune -l -q nproc
Parameter: nproc
Current: 4096
Planned: 4096
Default: (20+8*MAXUSERS)
Minimum: -
Module: -
Version: -
Dynamic: No
johnu17#

[Steven E. Protter]

Looks like you have kernel changes pending. Perhaps you increased nproc.

The change is not yet in production.

The two reports are consistent with a pending kernel change.

Looks like you need to carry it through and move the kernel to production. Or you can use sam to finish it up.

sam should show a pending value. Does it?

SEP

[twang]

"kmtune" command shows the value you set for the kernel parameter in your currently running kernel.
And sam shows it's planned value is 4098 (4096 + 2) after reboot.

[Bob Ballou]

Upon further review, here is what I found.
Problem system was patched last Saturday.
Problem showed up on Tuesday. I restored a pre-patched system on a test box. REstored maxuprc was set to 2459, which was consistent with what is in the /stand/system file. The only place I could find maxuprc set to (NPROC+2) was in a system file in /stand/build. Apparently, this /stand/build/system file was used when the system was rebooted after. On the recovered test system, I tried to dynamicly increase maxuproc to (NPROC+2) but got an out of range error. According to what I found on ITRC, maxuprc maximum value is ( NPROC-5). So SAM showed an illegal value; but the kernel build realized maxuprc was out of range and used the default.

Thanks for all your responses.