From owner-freebsd-bugs@freebsd.org Mon Aug 8 20:27:04 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F733BB30A8 for ; Mon, 8 Aug 2016 20:27:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 35238162D for ; Mon, 8 Aug 2016 20:27:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u78KR3IA004448 for ; Mon, 8 Aug 2016 20:27:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211528] [request] Mellanox ConnectX-3 drivers compiled into the base system Date: Mon, 08 Aug 2016 20:27:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mmacy@nextbsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2016 20:27:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211528 Matthew Macy changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmacy@nextbsd.org --- Comment #4 from Matthew Macy --- (In reply to Ben RUBSON from comment #3) There are two problems with this: The one that gives me say: 1) The linuxkpi that drm-next uses is very different from the linuxkpi in H= EAD. Adding COMPAT_LINUXKPI to HEAD would essentially preclude ever supporting anything newer than Haswell on FreeBSD with a GENERIC kernel config. It's s= afe to say that there are a lot more users of X11 on Intel hardware built within the last 3 years than there are IB users. The one that really bother me: 2) Once a driver is in GENERIC there is no established mechanism for removi= ng it. The kernel is reaching upwards of 30 MB. Unlike Linux and everything e= lse, FreeBSD has no namespacing for modules statically linked in to the kernel. = I've hit namespace conflicts between the linuxkpi and 20 year old raid drivers. = The driver has no reason to be there now and should have its own namespace even= if it does. FreeBSD is already several times slower booting than linux. A large part of this is due to the fact that it runs the probe routine for every PCI driver= at every PCI node in the device tree. Thus with any driver being added to GENERIC, the question should be: "is th= is device needed to work out of the box?" For drivers like em or igb the answe= r is yes. For most things the answer is no.=20 I assume that you're not really asking to further slow down boot times, blo= at the kernel, and create a perpetual burden on developers. What you probably really want is for device support to automatically load the modules as need= ed. If that's the case, take a look at Warner's initial work and see if you're = able to apply that to mlx:=20 http://bsdimp.blogspot.com/2016/01/details-on-coming-automatic-module.html --=20 You are receiving this mail because: You are the assignee for the bug.=