From owner-freebsd-net Fri Jul 7 9: 4: 2 2000 Delivered-To: freebsd-net@freebsd.org Received: from sofia.csl.sri.com (sofia.csl.sri.com [130.107.19.127]) by hub.freebsd.org (Postfix) with ESMTP id 4D6AA37C194 for ; Fri, 7 Jul 2000 09:03:44 -0700 (PDT) (envelope-from molter@sofia.csl.sri.com) Received: (from molter@localhost) by sofia.csl.sri.com (8.9.3/8.9.3) id JAA09878; Fri, 7 Jul 2000 09:05:03 -0700 (PDT) (envelope-from molter) From: Marco Molteni Date: Fri, 7 Jul 2000 09:05:03 -0700 To: net@FreeBSD.ORG Cc: Garrett Wollman Subject: Re: deleting cloned routes Message-ID: <20000707090503.A9860@sofia.csl.sri.com> Reply-To: net@FreeBSD.ORG References: <20000706192402.A25086@yahoo-inc.com> <200007071420.KAA37794@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200007071420.KAA37794@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Fri, Jul 07, 2000 at 10:20:04AM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 07 Jul 2000, Garrett Wollman wrote: > < said: > > > In Freebsd current, an incomplete connection is randomly dropped > > when the listen queue overflows. This logic could be easily extended > > by deleting the cloned route that is associated with the connection > > being dropped , if there is no information cached for that route. > > > Is this a reasonable fix ? > > It's a workable hack. I wouldn't call it a fix -- the real fix would > be to separate out the three functions currently bundled together in > the routing table into separate, more appropriate data structures. Garrett, as you may remember, I am interested in the routing code. Do you care to elaborate a little more about "separate out the three functions currently bundled together in the routing table" ? Thanks Marco -- Marco Molteni "rough consensus and running code" SRI International, System Design Laboratory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message