From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 00:53:59 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 633C4B7F; Mon, 9 Feb 2015 00:53:59 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4E7913C4; Mon, 9 Feb 2015 00:53:59 +0000 (UTC) Received: from AlfredMacbookAir.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 608FB341F90F; Sun, 8 Feb 2015 16:53:53 -0800 (PST) Message-ID: <54D805D1.4050008@freebsd.org> Date: Sun, 08 Feb 2015 16:56:49 -0800 From: Alfred Perlstein Organization: FreeBSD User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mike@karels.net, Eric Joyner Subject: Re: Fwd: Adding new media types to if_media.h References: <201502082241.t18MfjJc091202@mail.karels.net> In-Reply-To: <201502082241.t18MfjJc091202@mail.karels.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , Rui Paulo , "freebsd-net@freebsd.org" , John Baldwin , Jack Vogel , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 00:53:59 -0000 On 2/8/15 2:41 PM, Mike Karels wrote: > > To solve the second problem, I think the right approach would be to reduce > this interface to a truly generic one, such as media type (e.g. Ethernet), > generic flags, and perhaps generic status. Then there should be a separate > media-specific interface for each type, such as Ethernet and 802.11. To a > small extent, we already have that. Solving the second, more general problem, > requires a whole new driver KPI that will require surgery to every driver, > which is not an exercise that I would consider. > > > I am willing to do a prototype for -current for evaluation. > > Comments, alternatives, ? Mike, I think we have enough people to chip in that your concern about breaking the KPI is not as bad as you think. Would like to hear the first correct + long term + less hackish proposal first. Norse has a kernel team that is heavily invested in networking that can help with the transition. If done right, likely renaming ALL of the macros it will be quite trivial to catch all bad cases and move us forward in one great leap. -Alfred