[ECOS] Re: about elix

[ECOS] Re: about elix

[Fano Ramparany]

If by "dynamic creating thread" you mean creating a thread in the body
of another thread entry, then you don't need elix.
eCos supports the following:

void entry1(...)
{
    ...
    cyg_thread_create (...,thread_handle2,...);
    cyg_thread_resume (thread_handle2);
    ...
}

void cyg_user_start ()
{
    ...
    cyg_thread_create (...,entry1,...,thread_handle1,...);
    cyg_thread_resume (thread_handle1);
    ...
}


>Subject:    about elix
>Date:  Thu, 24 May 2001 14:30:18 +0800
>From: "wangwei" <wangw@start.com.cn>
>     To:   <ecos-discuss@sources.redhat.com>
> Hi,all
>I want some application with dynamic creating thread . So I must use
elix in
>ecos .
>Does anybody tell me if elix in ecos is stable?

[ECOS] Re: about elix

[wangwei]

I just mean create a thread in the body of anther thread , and the thread
can use dynamic memory as its
stack , when the thread ends, the memory of its stack can be released .
I want to know if ecos support this ?
thinks!
----- Original Message -----
From: "Fano Ramparany" <Fano.Ramparany@rd.francetelecom.fr>
To: <wangw@start.com.cn>
Cc: "eCos Disuss" <ecos-discuss@sourceware.cygnus.com>
Sent: Friday, May 25, 2001 3:36 PM
Subject: Re: about elix


> If by "dynamic creating thread" you mean creating a thread in the body
> of another thread entry, then you don't need elix.
> eCos supports the following:
>
> void entry1(...)
> {
>     ...
>     cyg_thread_create (...,thread_handle2,...);
>     cyg_thread_resume (thread_handle2);
>     ...
> }
>
> void cyg_user_start ()
> {
>     ...
>     cyg_thread_create (...,entry1,...,thread_handle1,...);
>     cyg_thread_resume (thread_handle1);
>     ...
> }
>
>
> >Subject:    about elix
> >Date:  Thu, 24 May 2001 14:30:18 +0800
> >From: "wangwei" <wangw@start.com.cn>
> >     To:   <ecos-discuss@sources.redhat.com>
> > Hi,all
> >I want some application with dynamic creating thread . So I must use
> elix in
> >ecos .
> >Does anybody tell me if elix in ecos is stable?

[ECOS] Re: about elix

[Fano Ramparany]

wangwei wrote:

> I just mean create a thread in the body of anther thread , and the thread
> can use dynamic memory as its
> stack , when the thread ends, the memory of its stack can be released .
> I want to know if ecos support this ?

In the applications I've developped so far thread stacks are preallocated
array variables. Embedded applications generally don't use dynamic memory
management (malloc). eCos provides an alternative mechanism called "memory
pool"
which might fit your needs.

Fano

Re: [ECOS] Re: about elix

[Hugo Tyson]

"wangwei" <wangw@start.com.cn> writes:

> I just mean create a thread in the body of anther thread , and the thread
> can use dynamic memory as its stack , when the thread ends, the memory of
> its stack can be released .

You must write the code to allocate the dynamic memory when you create the
thread and its stack, and you must write the code to free the dynamic
memory when the thread ends (in a different thread).

> I want to know if ecos support this ?

But all the calls are there, and there is nothing special about the memory
that is used for a thread object and its stack; you can allocate and free
it just like any other memory.

	- Huge

Re: [ECOS] Re: about elix

[wangwei]

Thanks.
I have realized it .The method is ok.
----- Original Message -----
From: "Hugo Tyson" <hmt@redhat.com>
To: <ecos-discuss@sources.redhat.com>
Sent: Friday, May 25, 2001 6:04 PM
Subject: Re: [ECOS] Re: about elix


>
> "wangwei" <wangw@start.com.cn> writes:
>
> > I just mean create a thread in the body of anther thread , and the
thread
> > can use dynamic memory as its stack , when the thread ends, the memory
of
> > its stack can be released .
>
> You must write the code to allocate the dynamic memory when you create the
> thread and its stack, and you must write the code to free the dynamic
> memory when the thread ends (in a different thread).
>
> > I want to know if ecos support this ?
>
> But all the calls are there, and there is nothing special about the memory
> that is used for a thread object and its stack; you can allocate and free
> it just like any other memory.
>
> - Huge
>
>