From owner-freebsd-virtualization@freebsd.org  Sat Jan 13 04:35:00 2018
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@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 510E8E72A7F
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Sat, 13 Jan 2018 04:35:00 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CB92B7339D;
 Sat, 13 Jan 2018 04:34:59 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1])
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w0D4YopI043281;
 Fri, 12 Jan 2018 20:34:50 -0800 (PST)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: (from freebsd-rwg@localhost)
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w0D4YoQv043280;
 Fri, 12 Jan 2018 20:34:50 -0800 (PST) (envelope-from freebsd-rwg)
From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
Message-Id: <201801130434.w0D4YoQv043280@pdx.rh.CN85.dnsmgr.net>
Subject: Re: ena(4) is not in GENERIC, now default for some/all instances on
 AWS EC2
In-Reply-To: <20180112190423.GC39759@ymer.vnode.se>
To: Joel Dahl <joel@vnode.se>
Date: Fri, 12 Jan 2018 20:34:50 -0800 (PST)
CC: Maxim Sobolev <sobomax@freebsd.org>, Marcin Wojtas <mw@semihalf.com>,
 freebsd-virtualization@freebsd.org, mk@semihalf.com
X-Mailer: ELM [version 2.4ME+ PL121h (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jan 2018 04:35:00 -0000

> On Thu, Jan 11, 2018 at 10:14:55AM -0800, Maxim Sobolev wrote:
> > Well, that might work, but I am curious why do we have all other network 40
> > or so drivers in the GENERIC but not this one. Considering significant
> > portion of FreeBSD systems deployed these days are going to be running on
> > the cloud this makes no sense to me. Is there some policy out there which
> > governs such decisions?
> 
> Email current@ and ask if there are any objections before you add it to
> GENERIC?

There is work going on in -current by Warner (imp@) called devmatch that
makes this issue go away and rips out all the other drivers from GENERIC
that can be automatically loaded by devmatch in the future.


-- 
Rod Grimes                                                 rgrimes@freebsd.org