Re: [lwip-users] [lwip users] using threads in our application safely ???

[Christiaan Simons]

>      I use the TFTP server from the linux system , not from the lwip
> .While getting a file from the remote server,  I can observe the
> first 512 bytes (which tftp server has to send ) on my client side ,
> using ethereal , but as I said  tapif_input halts after some time ,
> I thought it would be the problem from my TFTP client timeout
> mechanism , so I increased the timeout of my TFTP client , no change.

Ah, thus the TFTP client runs on top of lwip.

Does the server get a proper ACK from the client, in time?
The timeout of your server can play a major role here.

>      I created only a single thread , there are no multiple threads
> , I saw in one of the lwip message list that we should create a new
> thread for sending and receiving , I do not know about my
> application , whether to use multiple threads . I have no idea of
> threading  , So I asked for an explanation of the thread mechanism
> which can be used safely in our applications,

There are 2 examples in the contrib/ports/unix tree.
The 'simhost' example uses the netconn/socket api which you
probably use. Follow this as a reference.

>     Gprof , is ok with normal applications , but it has problems
> with threaded applications on Linux ,  Can we write an application
> on lwip  with out threading ...?`?? If so how can we do this...?

I just recommend not to use it.
Profiling won't help solving this issue anyway.

>   Please see the code when you find some time....
No.

Bye,

Christiaan Simons

Hardware / Software Engineer
Axon Digital Design

+31 (0)13 511 66 66
+31 (0)13 511 41 51

address@hidden
http://www.axon.tv



This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named.  If you are not the named addressee you should not
disseminate, distribute or copy this e-mail.