test: Bump up locked memory in lockmem tests

The default aggsize is 4M.  This is the dominant drain on locked
memory for a simple script like "BEGIN { @ = avg(1) }".

The lockmem tests check behavior when the lockmem limit is too
small; anything less than 4M is suitable.

They also check when the lockmem limit is large enough.  We were
using a lockmem limit of 16M, which is clearly inadequate even
for only a few CPUs.

Bump the "large enough" sizes up to 256M, which should be sufficient
even for dozens of CPUs.

Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>

test/unittest/misc/tst.lockmem-cmdline.sh

@@ -8,7 +8,7 @@
 
 dtrace=$1
 
-for val in 1 16384 unlimited; do
+for val in 1 262144 unlimited; do
 	ulimit -l $val
 
 	$dtrace -qn 'BEGIN { @ = avg(1234); exit(0); }'

test/unittest/misc/tst.lockmem-envvar.sh

@@ -10,7 +10,7 @@ dtrace=$1
 
 ulimit -l 1
 
-for val in 16 1K 16384K 16M unlimited; do
+for val in 16 1K 262144K 256M unlimited; do
 	DTRACE_OPT_LOCKMEM=$val $dtrace -qn 'BEGIN { @ = avg(1234); exit(0); }'
 	echo $?
 done

test/unittest/misc/tst.lockmem-pragma.sh

@@ -10,7 +10,7 @@ dtrace=$1
 
 ulimit -l 1
 
-for val in 16 1K 16384K 16M unlimited; do
+for val in 16 1K 262144K 256M unlimited; do
 	$dtrace -qs /dev/stdin << EOF
 		#pragma D option lockmem=$val
 

test/unittest/misc/tst.lockmem-x.sh

@@ -10,7 +10,7 @@ dtrace=$1
 
 ulimit -l 1
 
-for val in 16 1K 16384K 16M unlimited; do
+for val in 16 1K 262144K 256M unlimited; do
 	$dtrace -xlockmem=$val -qn 'BEGIN { @ = avg(1234); exit(0); }'
 	echo $?
 done