lwIP - A Lightweight TCP/IP stack - Bugs: bug #50698, Need separate sys_arch functions...
You are not allowed to post comments on this tracker with your current authentication level.
bug #50698: Need separate sys_arch functions for interrupt context
Submitter: | Daniel Elstner <danielk> | ||
Submitted: | Sat 01 Apr 2017 07:28:36 PM UTC | ||
Category: | Platform ports | Severity: | 1 - Wish |
Item Group: | Feature Request | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Jump to the original submission
Fri 05 Jan 2018 08:10:44 PM UTC, comment #6: |
Simon Goldschmidt <goldsimon> |
Thu 04 Jan 2018 04:45:06 PM UTC, comment #5: Any idea of how you would propagate the "BaseType_t *pxHigherPriorityTaskWoken" to the original ISR? For Cortex ports, we could invoke the scheduler directly, but not for a generic FreeRTOS port... |
Simon Goldschmidt <goldsimon> |
Thu 04 Jan 2018 06:57:17 AM UTC, comment #4: OK, reopened :-)
|
Simon Goldschmidt <goldsimon> |
Thu 04 Jan 2018 06:49:06 AM UTC, comment #3: Well, my initial minimal proposal was to only add a new tcpip_trycallback_from_isr() API function, which would not require the pbuf alloc if I remember things correctly. |
Daniel Elstner <danielk> |
Thu 04 Jan 2018 06:41:29 AM UTC, comment #2: Daniel, looking at this again I don't think it will work to adapt sys_arch to FreeRTOS:
|
Simon Goldschmidt <goldsimon> |
Wed 05 Apr 2017 07:22:09 PM UTC, comment #1: I'm aware of that freaky interrupt context interface FreeRTOS has. I don't know of any other OS doing it like that and honestly can't follow the argumentation of people telling me that doing it the FreeRTOS way is a performance improvement.
|
Simon Goldschmidt <goldsimon> |
Sat 01 Apr 2017 07:28:36 PM UTC, original submission:
Depending on the configuration, lwIP allows some operations to be executed from interrupt context. E.g. the static callback mechanism is intended to allow posting messages to the TCP/IP thread via tcpip_trycallback() directly from an interrupt handler.
|
Daniel Elstner <danielk> |
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 8 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-01-05 | goldsimon | Status | In Progress | Fixed | |
Open/Closed | Open | Closed | |||
2018-01-04 | goldsimon | Status | Wont Fix | In Progress | |
Open/Closed | Closed | Open | |||
2018-01-04 | goldsimon | Status | None | Wont Fix | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed | |||
2017-04-05 | goldsimon | Severity | 3 - Normal | 1 - Wish |
Powered by Savane 3.13-caa5.
Corresponding source code
I've decided to let the port handle this via the sys_mbox_trypost_fromisr() return value (which e.g. can be positive when scheduling is needed - normally all errors are negative).
I've pushed the lwIP core change for this and will be pushing an adaption for contrib soon.