On Thu, 2011-10-27 at 14:53 -0500, Dittrich, Matthew wrote: > > No other tasks/threads are involved, iqe_monitor_events() and > ethernetif_handlepackets() were discussed/posted previously. The only > place netif->input is called is in ethernetif_handlepackets(), any > application tcp_write()'s that result from ethernet_input() running > are safe right? Any tcp_write()'s from sys_check_timeouts() or > iqe_monitor_events() are certainly safe, because this is all happening > in the same (the only) thread calling any lwIP routines. Right?
That sounds fine. > I changed some constants in my MAC tx driver (from 18 256byte DMA > descriptors, to 3 1536 byte descriptors) and the machine ran all last > night without a failure. I didn't change any code logic, but it seems > to be working fine now... so either a bug in my descriptor handling > code is hiding very well, resulting in selective dropping of some > "unique" packets, or the chip is screwy (it's always fun to blame the > silicon! :). Anyway, those (now questionable) code paths that spread > the frame over multiple descriptors will never run because a full > frame can fit in a single one. For me, the issue is resolved. OK. I would certainly investigate those, but get back to us if you start to suspect the problem is within lwIP. > If you wouldn't mind, please take a look at the last pcap that I sent > yesterday Sorry, out of time (again)!. Kieran _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
