This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Thread model and software interrutps
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Samie Hassan Ghauri <samiehg at hotmail dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Fri, 1 Oct 2004 18:20:57 +0200
- Subject: Re: [ECOS] Thread model and software interrutps
- References: <BAY12-F6YsDSzhxRz3s00003619@hotmail.com>
On Fri, Oct 01, 2004 at 03:51:50PM +0000, Samie Hassan Ghauri wrote:
> Thanks for the reply.
>
> Could you briefly outline 'what kind of complexities' rise when the driver
> is written as a thread?
Something has to create the thread, keep track of its stack etc. You
have an extra layer of comminication, probably message passing which
will add overhead. You have the memory management of this message
passing. It can make debugging harder. It will generally need more
memory for the stack and the message passing buffers.
Your eCos configuration might not have a kernel so you don't
even have threads!
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