From owner-freebsd-current Wed May 20 04:05:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12683 for freebsd-current-outgoing; Wed, 20 May 1998 04:05:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12630 for ; Wed, 20 May 1998 04:05:05 -0700 (PDT) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id UAA03733; Wed, 20 May 1998 20:03:39 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98021914) with ESMTP id UAA05126; Wed, 20 May 1998 20:03:38 +0900 (JST) Message-Id: <199805201103.UAA05126@hotaka.csl.sony.co.jp> To: Julian Elischer cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: struct ifnet handling... In-reply-to: Your message of "Tue, 19 May 1998 11:43:14 MST." Date: Wed, 20 May 1998 20:03:38 +0900 From: Kenjiro Cho Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian said: >> if_index is evil and hsould be not used within the kernelinterfaces should >> become fully dynamic eventually. >> possibly a hash-table might be used to map between externally supplied >> if_index numbers and teh real pointers. Why is if_index evil? AFAIK, it isn't used as "index" in the kernel and can be used as a unique identifier from both kernel and user space. When a classifier checks the rules, it already has a pointer to the struct ifnet so that comparing if_index is cheap. --Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message