This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Error on Cyg_Counter::add_alarm
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Arkadi Grosman <ArkadiG at mobilesoft dot com dot au>
- Cc: "'atonizzo at lycos dot com'" <atonizzo at lycos dot com>,ecos-discuss at sources dot redhat dot com
- Date: Mon, 24 May 2004 09:20:48 +0200
- Subject: Re: [ECOS] Error on Cyg_Counter::add_alarm
- References: <CC2D42FB63F1FC47A12CBCB7A41482805B0D50@sydmail02.main.mobilesoft.com.au>
On Mon, May 24, 2004 at 09:13:11AM +1000, Arkadi Grosman wrote:
> I do not think there is a "rule of thumb". There is a crude way of founding
> out how much stack you need:
> In your development system ( it would typically have way more memory
> installed compared to production one ) allocate as much as you can for
> stacks and fill the stack mem space with some pattern ( eg AA55 ). Run the
> system under stress and see how much of "patterned" stack space was
> overwritten for every task. Set your production system stacks to these sizes
> plus some slack
eCos already have code to do this for you. Take a look at
CYGFUN_KERNEL_THREADS_STACK_MEASUREMENT
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss