[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: Simon Goldschmidt
Subject: [lwip-devel] [bug #1902] Timeouts and semaphores/mailboxes are too tightly integrated
Date: Wed, 16 May 2007 11:14:19 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20070309 Firefox/

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

Kieran, as at least one implementation in contrib relies on the integration
of timers with semaphores and tcpip.c relies on it with mboxes, maybe we see
this as a feature instead of a bug?

I'd say the user must know what he is doing if using lwip_timeout(). But
maybe we should remove calls to sys_sem_wait and sys_mbox_fetch from api
files (thus removing timeout processing from api threads and not provide this
feature to the users). This would effectively make sys_sem_wait unused
(besides the contrib files but maybe those files could be modified to use
mboxes for that) but we would not have to cope with users implementing
timeouts in a wrong way.


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

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