Frédéric BERNON wrote:
But, if the main() task handle the ARP Timer (and read/write the arp table), and if tcpip_thread also read/write in arp table, is the corruption possible?
It's theoretically possible I guess: it would imply the tcpip thread didn't have a chance to run until the ARP timeout triggered. Improbable but possible.
Perhaps, as you suggest, it will be better to put arp_timer initialization directly in the callback (to be in another file than the tcpip.c, but in the same thread than the tcpip_thread)...
It seems that would be the best course then. I'm not sure if there's any appropriate place to document this so people are aware of the issue.
Jifl -- eCosCentric Ltd http://www.eCosCentric.com/ The eCos and RedBoot experts ** Visit us at ESC Silicon Valley <http://www.embedded.com/esc/sv> ** ** April 3-5 2007, Booth 1922, San Jose McEnery Convention Center ** Company legal info, address and number: http://www.ecoscentric.com/legal ------["The best things in life aren't things."]------ Opinions==mine _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
