lwIP - A Lightweight TCP/IP stack - Bugs: bug #48220, TCPIP_CORE_LOCKING should be the...
You are not allowed to post comments on this tracker with your current authentication level.
bug #48220: TCPIP_CORE_LOCKING should be the default
Submitter: | Simon Goldschmidt <goldsimon> | ||
Submitted: | Tue 14 Jun 2016 07:30:14 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | 2.0.0 Beta2 |
lwIP version: | git head |
Thu 30 Jun 2016 08:39:21 PM UTC, comment #4: |
Simon Goldschmidt <goldsimon> |
Thu 30 Jun 2016 08:24:35 PM UTC, comment #3: Right. And it's probably not the only occurrence, so this might not be a good idea... |
Simon Goldschmidt <goldsimon> |
Tue 28 Jun 2016 01:42:15 PM UTC, comment #2: Simon,
*/
|
Joel Cunningham <jcunningham> |
Mon 27 Jun 2016 08:59:40 AM UTC, comment #1: We might want to change 'tcpip_callback()' (not the non-blocking version) to use LOCK_TCPIP_CORE() instead of posting a message.
|
Simon Goldschmidt <goldsimon> |
Tue 14 Jun 2016 07:30:14 AM UTC, original submission:
LWIP_TCPIP_CORE_LOCKING should perform much better since grabbing a mutex should be faster than 2 thread context switches on most platforms. Also, thread priorites help to schedule which task is served first.
|
Simon Goldschmidt <goldsimon> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-06-30 | goldsimon | Status | None | Fixed | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed | |||
2016-06-30 | goldsimon | Planned Release | None | 2.0.0 Beta2 |
Powered by Savane 3.13-f8d8.
Corresponding source code
Done.
Define LWIP_COMPAT_MUTEX_ALLOWED if you really need to use LWIP_TCPIP_CORE_LOCKING && LWIP_COMPAT_MUTEX (which is not a good idea since only mutexes can prevent priority inversion).