aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKOSAKI Motohiro2012-05-31 18:26:33 -0500
committerLinus Torvalds2012-05-31 19:49:31 -0500
commitcef0184c115e5e4e10498f6548d9526465e72478 (patch)
tree752c4116e0f93328239db9ff2c2ed730fef3ce0e /tools/testing/selftests
parentfd1f87d24d492fda464bedf10a5dd5174ff9b065 (diff)
downloadkernel-omap-cef0184c115e5e4e10498f6548d9526465e72478.tar.gz
kernel-omap-cef0184c115e5e4e10498f6548d9526465e72478.tar.xz
kernel-omap-cef0184c115e5e4e10498f6548d9526465e72478.zip
mqueue: separate mqueue default value from maximum value
Commit b231cca4381e ("message queues: increase range limits") changed mqueue default value when attr parameter is specified NULL from hard coded value to fs.mqueue.{msg,msgsize}_max sysctl value. This made large side effect. When user need to use two mqueue applications 1) using !NULL attr parameter and it require big message size and 2) using NULL attr parameter and only need small size message, app (1) require to raise fs.mqueue.msgsize_max and app (2) consume large memory size even though it doesn't need. Doug Ledford propsed to switch back it to static hard coded value. However it also has a compatibility problem. Some applications might started depend on the default value is tunable. The solution is to separate default value from maximum value. Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Signed-off-by: Doug Ledford <dledford@redhat.com> Acked-by: Doug Ledford <dledford@redhat.com> Acked-by: Joe Korty <joe.korty@ccur.com> Cc: Amerigo Wang <amwang@redhat.com> Acked-by: Serge E. Hallyn <serue@us.ibm.com> Cc: Jiri Slaby <jslaby@suse.cz> Cc: Manfred Spraul <manfred@colorfullife.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools/testing/selftests')
0 files changed, 0 insertions, 0 deletions