Re: [ECOS] Macro that ensures minimum stack size

[Nick Garnett <nickg at ecoscentric dot com>]

Bart Veer <bartv@ecoscentric.com> writes:

> >>>>> "Nick" == Nick Garnett <nickg@ecoscentric.com> writes:
>     Nick> The amount of stack needed for an application is usually
>     Nick> fairly independent of the exact architecture. To me this
>     Nick> seems a safer approach than yours, since it guarantees that
>     Nick> the app stack space is always present.
> 
> Actually, the synthetic target does require rather larger stacks than
> other architectures. Because of the way interrupts are handled you can
> end up with a couple of Linux signal contexts on an eCos thread stack,
> and those need quite a lot of memory. To compensate for this
> CYGNUM_HAL_STACK_SIZE_MINIMUM and CYGNUM_HAL_STACK_SIZE_TYPICAL are
> set to suitably large values, so it is still correct to use those when
> defining application stacks.
> 

I don't see how this differs from what I said. All the extra system
requirements are catered for in CYGNUM_HAL_STACK_SIZE_MINIMUM, leaving
the user to just work out and add what the application's stack usage
is, which should be fairly constant.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss