[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: [lwip-users] Task priorities in TCP/IP Stack
From: |
Wenger Dominik |
Subject: |
AW: [lwip-users] Task priorities in TCP/IP Stack |
Date: |
Wed, 24 Feb 2010 15:57:15 +0100 |
...
Now I see, that the ETHINT task don't use messages to commit the
received frames to the TCP/IP task. It calls ethernet_input() directly.
This depends, that two tasks work with the stack and the data structures
are not ever constistent (read-modify-write). I receive a lot of
assertions.
...
Your ETHINT Task should use netif->input() to pass the pbufs and not
ethernet_input() directly. Calling ethernet_input directly is not
allowed, and will cause multithreading problems.