Date: Fri, 01 Jan 2021 20:40:07 +0000 From: =?utf-8?Q?Mina_Gali=C4=87?= <me+freebsd@igalic.co> To: Allan Jude <allanjude@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Enabling AESNI by default Message-ID: <q5MkIX7Ec_BtKC4dL9hH3qckAaiLI1iNYgU80k1qodEU64kc9LtnPnqcaqZw7TlhJ4106Owq1r4Elxh03m4uKNu5dTbqL2xNAZA6AE3QCrM=@igalic.co> In-Reply-To: <5d56280e-a8dd-b28d-7039-f8fe0bc0cd6f@freebsd.org> References: <5d56280e-a8dd-b28d-7039-f8fe0bc0cd6f@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, December 31st, 2020 at 20:51, Allan Jude <allanjude@freebsd.or= g> wrote: > We've had the AESNI module for quite a few years now, and it has not caus= ed any problems. > > I am wondering if there are any objections to including it in GENERIC, so= that users get the benefit without having to have the "tribal knowledge" t= hat 'to accelerate kernel crypto (GELI, ZFS, IPSEC, etc), you need to load = aesni.ko' This tribal knowledge is encoded in bsdinstall when you setup encryption on= zfs: https://cgit.freebsd.org/src/tree/usr.sbin/bsdinstall/scripts/zfsboot#n1207 Mina
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?q5MkIX7Ec_BtKC4dL9hH3qckAaiLI1iNYgU80k1qodEU64kc9LtnPnqcaqZw7TlhJ4106Owq1r4Elxh03m4uKNu5dTbqL2xNAZA6AE3QCrM=>