lwIP - A Lightweight TCP/IP stack - Bugs: bug #48568, timeouts does not support late...
You are not allowed to post comments on this tracker with your current authentication level.
bug #48568: timeouts does not support late firing properly
Submitter: | Sylvain Rochet <gradator> | ||
Submitted: | Wed 20 Jul 2016 10:07:28 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | 2.0.0 Beta2 |
lwIP version: | git head |
Wed 27 Jul 2016 07:28:23 PM UTC, comment #4: |
Simon Goldschmidt <goldsimon> |
Wed 27 Jul 2016 07:20:29 PM UTC, comment #3: Absolute timers are great, and faster, because the comparison is obviously the most simple comparison that could be made, well, at least, on 32-bit targets (are there still users of lwIP on 8-bit platforms ?, that doesn't sound like a good design choice nowadays ;-), I'm pretty none of us tried that for a long time).
|
Sylvain Rochet <gradator> |
Wed 27 Jul 2016 07:06:17 PM UTC, comment #2:
|
Simon Goldschmidt <goldsimon> |
Wed 20 Jul 2016 10:09:19 AM UTC, comment #1: This could be fixed by moving to absolute target timers instead of the currently used delta-diff timers (which I dislike, due to the problem mentioned below, at least). The main problem is our current support of timers restart on wake up event for devices that sleep to prevent firing all timers at once, that's hard to achieve with absolute target timers.
|
Sylvain Rochet <gradator> |
Wed 20 Jul 2016 10:07:28 AM UTC, original submission:
With the current code, timeouts get delayed when we are in a debugger breakpoint and sys_now() might continues running while we are stopped (e.g. when it uses a clock source from an OS which does not stop).
|
Sylvain Rochet <gradator> |
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-07-27 | goldsimon | Status | None | Fixed | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-caa5.
Corresponding source code
I've fixed this bug, can we continue the diff-time vs. absolute-time in a seperate task, or reuse patch #7855?
Hey, I've tried lwIP on an ATmega just ~2 years ago, andi t worked! (OK, I only had a slipif and needed a slipif-to-ethernet router on my PC...) But that was no a real-world thing, of course... ;-)