|
From: | Artem Pisarenko |
Subject: | Re: [lwip-users] Assertion "memp sanity" failed at line 463in../lwip_1_4_0/Src/core/memp.c |
Date: | Mon, 19 Nov 2012 15:24:12 +0700 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 |
19.11.2012 14:07, Mikael Eiman wrote:
Agree. Furthermore, driver thread may perform other unseful tasks in simple and sequentially manner. The only cost is memory usage for task stack. Other overheads are close to zero.One easy way to get around this kind of trouble is to not do any lwIP calls from the interrupt handler - just notify the network thread of the pending data and let it handle it when it gets its turn. It won't perform quite as well, but make the network task high priority and the difference should be close to zero in most cases.
[Prev in Thread] | Current Thread | [Next in Thread] |