From owner-freebsd-current  Thu Feb  1 13:30:19 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA01537
          for current-outgoing; Thu, 1 Feb 1996 13:30:19 -0800 (PST)
Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA01529
          for <current@freebsd.org>; Thu, 1 Feb 1996 13:30:13 -0800 (PST)
Received: from critter.tfs.com ([193.88.44.194]) by ra.dkuug.dk (8.6.12/8.6.12) with ESMTP id WAA10155; Thu, 1 Feb 1996 22:17:45 +0100
Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id WAA00995; Thu, 1 Feb 1996 22:07:58 +0100
X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol
To: Nate Williams <nate@sri.MT.net>
cc: michael butler <imb@scgt.oz.au>, current@freebsd.org
Subject: Re: ip_fw ordering of rules.. 
In-reply-to: Your message of "Thu, 01 Feb 1996 11:30:40 MST."
             <199602011830.LAA20539@rocky.sri.MT.net> 
Date: Thu, 01 Feb 1996 22:07:57 +0100
Message-ID: <993.823208877@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@freebsd.org
Precedence: bulk

> > > It is always a singled linked list anyway...
> >  
> > Ugh ! Then there'll be no disadvantage in removing the "sort" :-)
> 
> Except that supposedly it 'orders' things so that the most common rules
> (or what it thinks should be most common) will be found at the top, thus
> making it faster since you don't have to walk the entire tree.

Well, I suggest you look at the ordering then, that is most
certainly >NOT< what the code does.

I will make it an option.

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.