jblackarty wrote: > My aim is to form a something like "network domain", which will > include lwip, ethernet driver, network-related application threads and > associated data. Their crash must be separated from the entire system.
Given the nature of network communication, for such clean separation, you would have to create an API layer that does not need communicating threads to share memory with lwIP. The most tricky part here would be sharing TX/RX data between those threads: to prevent having a priviledged-mode handler copying the data between protection regions, you would have to adapt memory protection on the fly (i.e. or TX data, TX pbuf's contents may be written by the application thread and read by lwIP, for RX, lwIP may write and the application may read only). However, although this seems interesting, lwIP's design is far away from this (yet?). Simon _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
