net.core.rmem_default is larger than net.core.rmem_max
Subsystems (2)
It's unconventional that "default" value is greater than "max". :-(
net.core.rmem_max = 131071
net.core.rmem_default = 229376
net.core.wmem_max = 131071
net.core.wmem_default = 229376
And bisect the code to find the following commit caused this phenomenon. This patch increase SK_WMEM_MAX and SK_RMEM_MAX which are used to initialize them.
But rmem_max and wmem_max value are still be covered according the RAM size in sk_init().
87fb4b7b533073eeeaed0b6bf7c2328995f6c075 is the first bad commit commit 87fb4b7b533073eeeaed0b6bf7c2328995f6c075
Author: Eric Dumazet <[email protected]> Date: Thu Oct 13 07:28:54 2011 +0000
net: more accurate skb truesize
Shan Wei said, at 2012/4/27 17:31:
Quoted 5 lines
It's unconventional that "default" value is greater than "max". :-(
net.core.rmem_max = 131071
net.core.rmem_default = 229376
ping......
I have no idea to fix this.
Maybe add rmem_max value to be greater than rmem_default? Eric, can you look into this?
Quoted 19 lines
net.core.wmem_max = 131071
net.core.wmem_default = 229376And bisect the code to find the following commit caused this phenomenon. This patch increase
SK_WMEM_MAXandSK_RMEM_MAXwhich are used to initialize them.
Butrmem_maxandwmem_maxvalue are still be covered according the RAM size insk_init().
87fb4b7b533073eeeaed0b6bf7c2328995f6c075is the first bad commit commit87fb4b7b533073eeeaed0b6bf7c2328995f6c075Author: Eric Dumazet <[email protected]> Date: Thu Oct 13 07:28:54 2011 +0000net: more accurate skb truesize