Date: Sat, 3 Mar 2001 18:26:53 -0800 (PST) From: Archie Cobbs <archie@dellroad.org> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/25517: ARP cache timeout behavior can be improved Message-ID: <200103040226.f242QrJ32138@arch20m.dellroad.org>
next in thread | raw e-mail | index | archive | help
>Number: 25517 >Category: kern >Synopsis: ARP cache timeout behavior can be improved >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Mar 03 18:40:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Archie Cobbs >Release: FreeBSD 4.2-RELEASE i386 >Organization: Packet Design, Inc. >Environment: All current versions of FreeBSD >Description: When an ARP entry expires after 15 minutes, the ARP entry is simply deleted from the ARP cache. Then the next packet(s) destined for the other host are delayed while a new ARP query and response takes place. This delay is unnecessary and disruptive for certain protocols that are sensitive to jitter. Moreover, as network speeds increase while ARP query/response cycles continue to take roughly the same amount of time, this effect will become more and more pronounced. This problem should be easy to fix... > From: Stephen Casner <casner@packetdesign.com> > > The suggested enhancement is to _not_ flush an arp cache > entry when its timer expires. Instead, go ahead and send > the arp request, but continue using the cache entry to send > packets. If there is no response to the arp request after > the number of retries specified in the protocol, then flush > the cache entry. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103040226.f242QrJ32138>