[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #48220] TCPIP_CORE_LOCKING should be the default
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #48220] TCPIP_CORE_LOCKING should be the default |
Date: |
Tue, 14 Jun 2016 07:30:17 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36 |
URL:
<http://savannah.nongnu.org/bugs/?48220>
Summary: TCPIP_CORE_LOCKING should be the default
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: goldsimon
Submitted on: Tue 14 Jun 2016 07:30:14 AM GMT
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: 2.0.0 Beta2
lwIP version: git head
_______________________________________________________
Details:
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.
However, we should get people to implement a mutex to prevent priority
inversion.
To do this, we could raise an #error if LWIP_COMPAT_MUTEX is 1. (and we should
implement mutexes for our example ports :)
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?48220>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #48220] TCPIP_CORE_LOCKING should be the default,
Simon Goldschmidt <=