From owner-freebsd-virtualization@freebsd.org  Fri Jan 12 19:04:27 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 8A3C7E76892
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Fri, 12 Jan 2018 19:04:27 +0000 (UTC) (envelope-from joel@vnode.se)
Received: from oden.vnode.se (oden.vnode.se
 [IPv6:2001:19f0:6c01:6b7:5400:1ff:fe33:16b1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "oden.vnode.se", Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4E6247A8D4;
 Fri, 12 Jan 2018 19:04:27 +0000 (UTC) (envelope-from joel@vnode.se)
Received: from ymer.vnode.se (62-20-154-136-no280.tbcn.telia.com
 [62.20.154.136])
 by oden.vnode.se (Postfix) with ESMTPSA id A3C1C1F69C;
 Fri, 12 Jan 2018 20:04:24 +0100 (CET)
Date: Fri, 12 Jan 2018 20:04:24 +0100
From: Joel Dahl <joel@vnode.se>
To: Maxim Sobolev <sobomax@freebsd.org>
Cc: Pete Wright <pete@nomadlogic.org>, Marcin Wojtas <mw@semihalf.com>,
 freebsd-virtualization@freebsd.org, mk@semihalf.com
Subject: Re: ena(4) is not in GENERIC, now default for some/all instances on
 AWS EC2
Message-ID: <20180112190423.GC39759@ymer.vnode.se>
Mail-Followup-To: Maxim Sobolev <sobomax@freebsd.org>,
 Pete Wright <pete@nomadlogic.org>, Marcin Wojtas <mw@semihalf.com>,
 freebsd-virtualization@freebsd.org, mk@semihalf.com
References: <CAH7qZftm=J9N4TqEsTY9fdxw0RSAy-Y7ROJ8_4r21x7xHu8xqw@mail.gmail.com>
 <3b5baa95-e87e-a527-5917-777ba0d6bca4@nomadlogic.org>
 <CAH7qZfvxWxFd-qEiG4gfDBkD68xzDb=uNS4Nnptp0EjcWoE+Rw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAH7qZfvxWxFd-qEiG4gfDBkD68xzDb=uNS4Nnptp0EjcWoE+Rw@mail.gmail.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
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: Fri, 12 Jan 2018 19:04:27 -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?

-- 
Joel