[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [lwip-users] sys_timeout

From: Curt McDowell
Subject: RE: [lwip-users] sys_timeout
Date: Mon, 6 Mar 2006 11:30:07 -0800


The way sys_arch is implemented, timeouts can only fire when the main process 
is sleeping on a semaphore or mailbox using either
sys_sem_wait() or sys_mbox_fetch() in src/core/sys.c.

I think it's an architectural deficiency that any of sys_arch is implemented in 
the lwip core.  The whole idea of sys_arch is to
provide a system abstraction, but currently it's difficult to replace 
sys_timeout() and other sys_arch functionality with a native
O/S implementation.  Worse, any application that wants to use lwip is forced to 
be based on lwip's sys_arch primitives.

Curt McDowell
Broadcom Corp.

> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden On 
> Behalf Of Christiaan Simons
> Sent: Wednesday, March 01, 2006 8:17 AM
> To: address@hidden
> Subject: [lwip-users] sys_timeout
> Hi,
> I'm struggling to get the ip_timer fired from the code in 
> lwip/src/api/tcpip.c (using sys_timeout). see CVS head.
> Does anyone encountered similar problems before?
> Bye,
> Christiaan Simons
> Hardware Designer
> Axon Digital Design
> 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.
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users

reply via email to

[Prev in Thread] Current Thread [Next in Thread]