[Top][All Lists]

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

[lwip-devel] [bug #1902] Timeouts and semaphores/mailboxes are too tight

From: Frédéric Bernon
Subject: [lwip-devel] [bug #1902] Timeouts and semaphores/mailboxes are too tightly integrated
Date: Wed, 16 May 2007 13:01:25 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv: Gecko/20070309 Firefox/

Follow-up Comment #28, bug #1902 (project lwip):

>- the timeouts/mailbox integration is a feature that is needed by tcpip.c
and therefore (at least in my opinion) not a bug.
>- the timeouts/semaphore integration is not needed / lead to bugs in the
past since normally a thread is not in a state to let timeouts run if waiting
for a semaphore (since most of the time semaphores are used as mutexes in lwip
code) therefore the timeout/semaphore integration could be thrown away
reducing sys_sem_wait to a direct call to sys_arch_sem_wait 

We have already talk about that in several others threads, but isn't it the
time to tell that internal lwIP features shouldn't have to be used "outside"
lwIP ? I think to sys_mbox_post which could be replace by direct calls to
sys_arch_mbox_fetch in most of cases (in fact, I think in all cases, except


Reply to this item at:


  Message posté via/par Savannah

reply via email to

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