[lwip-users] Re: [lwip] sys_thread_new Newbie question

[Duncan Palmer]

On Wednesday 17 July 2002 12:30, kevin stokes wrote:
> Thanks very much for your assistance.
>
> The DSP/BIOS docs don't specify that the threads delete themselves on exit.
> They imply that the threads hang around with a TERMINATED flag after they
> exit, so I assume I'll have write code to deal with it.

The threads used by LWIP run for the length of time the stack is up, so if 
you plan to have the TCP/IP stack running the whole time, they'll never exit. 
So, its really not worth spending much time dealing with thread termination.

>
> Thanks again for your help with this question.
>
> -Kevin Stokes
>
>
> From: Kieran Mansley <address@hidden>
>
> >Reply-To: address@hidden
> >To: address@hidden
> >Subject: Re: [lwip] sys_thread_new Newbie question
> >Date: Tue, 16 Jul 2002 21:18:36 +0100 (BST)
> >
> >On Tue, 16 Jul 2002, kevin stokes wrote:
> > > Greetings,
> > >   I'm attempting to port lwIP to TI's DSP/BIOS operating system.
> > >
> > >   So far, I'm very pleased with lwIP, and it looks like it will be
> >
> >perfect
> >
> > > for my application.
> > >
> > >   The DOC says you can implement sys_thread_new() if you like.  Some
> > > questions about that:
> > >
> > > 1.) If I want to start out without it, how do I go about specifying
> >
> >that, so
> >
> > > I don't have to implement sys_thread_new()?
> >
> >I take if you've read http://www.sics.se/~adam/lwip/os.html
> >
> >You don't explicitly have to specify anything, just alters the parts of
> >lwip that you can make use of.  Also, you're responsible for calling the
> >tcp_tmr() function as it can't be implemented as a separate thread.
> >
> > > 2.) sys_thread_new() creates a new thread, but what destroys it?  Are
> > > we supposed to implement code that knows when the (given) function
> > > returns
> >
> >and
> >
> > > then delete the thread?   If we don't explicitly delete the thread,
> > > then
> >
> >RAM
> >
> > > will be wasted..
> >
> >Usually threads destroy themselves when their path of execution comes to
> >an end.  This is the same as the way a program destroys itself when you
> >call exit(), or main() returns, or whatever - you don't have to do
> >anything to clean it up.  I'm not familiar with the operating system
> >you're working with, so no idea if that's the case there.
> >
> >Hope that helps,
> >
> >Kieran
> >
> >[This message was sent through the lwip discussion list.]
>
> _________________________________________________________________
> Join the world’s largest e-mail service with MSN Hotmail.
> http://www.hotmail.com
>
> [This message was sent through the lwip discussion list.]
[This message was sent through the lwip discussion list.]