From eb75c053eb46cbeb4ad9c0b7b179ba1acb20eba4 Mon Sep 17 00:00:00 2001 From: gdisirio Date: Sat, 28 Feb 2009 09:39:02 +0000 Subject: Added new benchmarks about semaphores and mutexes to the test suite. git-svn-id: svn://svn.code.sf.net/p/chibios/svn/trunk@804 35acf78f-673a-0410-8e92-d51de3d6d3f4 --- docs/src/stacks.dox | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'docs/src') diff --git a/docs/src/stacks.dox b/docs/src/stacks.dox index e824ea04a..a27c2e1b9 100644 --- a/docs/src/stacks.dox +++ b/docs/src/stacks.dox @@ -33,7 +33,8 @@ * stack. This is an important feature in a multithreaded environment, * without a dedicated interrupt stack each thread has to reserve * enough space, for interrupts servicing, within its own stack. This space, - * multiplied by the total threads number, can be a significant RAM waste. + * multiplied by the total threads number, can amount to a significant RAM + * overhead. * - Thread Stack, each thread has a dedicated stack for its own * execution and context switch. * - Other Stacks, some architectures (ARM) can have other stacks but @@ -46,7 +47,7 @@ * Assign too much space to a stack wastes RAM, assign too little space * leads to crashes or, worst scenario, hard to track instability. * - *

Assign the correct size

+ *

Assigning the correct size

* You may try to examine the asm listings in order to calculate the exact * stack requirements but this requires much time, experience and patience.
* An alternative way is to use an interactive method. Follow this procedure @@ -78,7 +79,7 @@ * . *

Final Notes

* Some useful info: - * - Stack overflows are the most common source of problems during development, + * - Stack overflows are the most common problems source during development, * when in trouble with crashes or anomalous behaviors always first verify * stack sizes. * - The required stack size can, and very often does change when changing -- cgit v1.2.3