From owner-freebsd-bugs Sat Mar 3 18:40: 7 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A761837B719 for ; Sat, 3 Mar 2001 18:40:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f242e1822251; Sat, 3 Mar 2001 18:40:01 -0800 (PST) (envelope-from gnats) Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id AE79137B719 for ; Sat, 3 Mar 2001 18:30:02 -0800 (PST) (envelope-from archie@dellroad.org) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id SAA37086 for ; Sat, 3 Mar 2001 18:27:02 -0800 (PST) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.1/8.11.1) id f242QrJ32138; Sat, 3 Mar 2001 18:26:53 -0800 (PST) (envelope-from archie) Message-Id: <200103040226.f242QrJ32138@arch20m.dellroad.org> Date: Sat, 3 Mar 2001 18:26:53 -0800 (PST) From: Archie Cobbs Reply-To: archie@dellroad.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/25517: ARP cache timeout behavior can be improved Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >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 > > 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