[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [task #6827] etharp could need some tuning
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [task #6827] etharp could need some tuning |
Date: |
Fri, 27 Apr 2007 19:23:03 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 |
Follow-up Comment #5, task #6827 (project lwip):
OK, http://lists.gnu.org/archive/html/lwip-devel/2006-04/msg00000.html
suggests to disable ARP table update from incoming IP packets. Still, ARP
broadcasts (gratuitous ARP?) could, on a big network like we have for
testing, fill the ARP table, so I made it quite big which slows it down.
I would implement the one-entry cache and optionally including a list instead
of an array to allow fast reordering of the entries. When find_entry gives
back a pointer to a struct etharp_entry instead of an index, this could be
switched mostly by including a different find_entry() function.
I'd make this a compiletime option as I think on really small networks the
array is still the best solution (and of course, the smallest, regarding code
size).
As to
>in current implementation, ethhdr->type is hardcoded to ETHTYP_IP)
I think renaming etharp_output() to etharp_output_ip() should be enough since
etharp is only used with IP packets... But then again, this would
unnecessarily break the ports, so I'll guess we'll leave it like it is.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/task/?6827>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/