summaryrefslogtreecommitdiff
path: root/apps/examples/ostest/Kconfig
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-11-05 20:02:56 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-11-05 20:02:56 +0000
commit457f849544b54a0ba4c773e082b37c34fa726268 (patch)
treebdd380d9b47ff56c649468de2983d0516739beed /apps/examples/ostest/Kconfig
parent45630c3d55a534689f83fd8871c06399934645e1 (diff)
downloadnuttx-457f849544b54a0ba4c773e082b37c34fa726268.tar.gz
nuttx-457f849544b54a0ba4c773e082b37c34fa726268.tar.bz2
nuttx-457f849544b54a0ba4c773e082b37c34fa726268.zip
Make ostest RR scheduler test use less memory from Freddie Chopin; Plus build fix from Darcy Gong
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5314 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'apps/examples/ostest/Kconfig')
-rw-r--r--apps/examples/ostest/Kconfig29
1 files changed, 29 insertions, 0 deletions
diff --git a/apps/examples/ostest/Kconfig b/apps/examples/ostest/Kconfig
index 0da7e4ce3..3c64dc0c6 100644
--- a/apps/examples/ostest/Kconfig
+++ b/apps/examples/ostest/Kconfig
@@ -39,4 +39,33 @@ config EXAMPLES_OSTEST_NBARRIER_THREADS
is 8 but a smaller number may be needed on systems without sufficient memory
to start so many threads.
+config EXAMPLES_OSTEST_RR_RANGE
+ int "Round-robin test - end of search range"
+ default 10000
+ range 1 32767
+ depends on RR_INTERVAL > 0
+ ---help---
+ During round-robin scheduling test two threads are created. Each of the threads
+ searches for prime numbers in the configurable range, doing that configurable
+ number of times.
+
+ This value specifies the end of search range and together with number of runs
+ allows to configure the length of this test - it should last at least a few
+ tens of seconds. Allowed values [1; 32767], default 10000
+
+config EXAMPLES_OSTEST_RR_RUNS
+ int "Round-robin test - number of runs"
+ default 10
+ range 1 32767
+ depends on RR_INTERVAL > 0
+ ---help---
+ During round-robin scheduling test two threads are created. Each of the threads
+ searches for prime numbers in the configurable range, doing that configurable
+ number of times.
+
+ This value specifies the number of times the thread searches the range for
+ prime numbers and together with end of search range allows to configure the
+ length of this test - it should last at least a few tens of seconds. Allowed
+ values [1; 32767], default 10
+
endif