|
From: | Simon Goldschmidt |
Subject: | [lwip-devel] [bug #1902] Timeouts and semaphores/mailboxes are too tightly integrated |
Date: | Wed, 16 May 2007 11:27:16 +0000 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 |
Follow-up Comment #26, bug #1902 (project lwip): OK, what I'm saying is: - 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 I think you originally said you wanted to wait for my timestamp changes to close this bug. All I'm saying now is I think there's no need to wait. If we throw away semaphore/timeout integration we can do it now. If not, we can close this bug as won't fix. Timeout/mailbox integration is needed anyway. _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?1902> _______________________________________________ Nachricht geschickt von/durch Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |