From owner-freebsd-hackers Mon Dec 28 22:00:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21922 for freebsd-hackers-outgoing; Mon, 28 Dec 1998 22:00:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA21917 for ; Mon, 28 Dec 1998 22:00:14 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zusC6-0006T3-00; Mon, 28 Dec 1998 22:59:50 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id WAA23091; Mon, 28 Dec 1998 22:58:01 -0700 (MST) Message-Id: <199812290558.WAA23091@harmony.village.org> To: Peter Wemm Subject: Re: How do I ... Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 29 Dec 1998 13:53:28 +0800." <199812290553.NAA70876@spinner.netplex.com.au> References: <199812290553.NAA70876@spinner.netplex.com.au> Date: Mon, 28 Dec 1998 22:58:00 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812290553.NAA70876@spinner.netplex.com.au> Peter Wemm writes: : The catch is that the driver in question has to support unloading. All the : existing network interfaces are pseudo-modules and only have a load : routine. Obviously this requires a fair amount of work to detach a network : interface from the stack (including cleaning up routing tables, pcbs, : queued data, etc) - nobody has done this yet as far as I'm aware. I : suspect there is a fair amount of infrastructure required to implement : this. I suspect that you are right. I've been looking at all of the existing drivers (since I'm writing a new one), and have found they all cheat and use the compatibility cruft. And even if they didn't cheat, they would have a heck of a time untangling things. I suspect that you are right. I had hoped to get away from understanding those internals. It may make sense to have a "if_dead" that is similar to deadfs where all "orphaned" interfaces go when they die. Hmmm, I'll have to look at this more closely.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message