From owner-freebsd-geom@FreeBSD.ORG Thu May 3 19:50:56 2012 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00089106566C for ; Thu, 3 May 2012 19:50:55 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id A35CB8FC15 for ; Thu, 3 May 2012 19:50:55 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 191C66D4; Thu, 3 May 2012 21:41:19 +0200 (CEST) Date: Thu, 3 May 2012 21:39:38 +0200 From: Pawel Jakub Dawidek To: Ilias-Dimitrios Vrachnis Message-ID: <20120503193938.GD1397@garage.freebsd.pl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DO5DiztRLs659m5i" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-geom@freebsd.org Subject: Re: A question about geli and aesni X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 May 2012 19:50:56 -0000 --DO5DiztRLs659m5i Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 29, 2012 at 05:46:27AM +0300, Ilias-Dimitrios Vrachnis wrote: > Hello, I have a question about the aesni integration with geli: >=20 > I use a geli encrypted root, on an aesni-capable cpu, and I noticed > that the .eli device is not hardware accelerated even though aesni.ko > is loaded (from loader.conf and not kld_list). > I have a suspicion that this happens because I did not load the module > before running geli init, but I cannot confirm it at the moment. It doesn't matter what was available during 'geli init'. > Running geli init on an md device after the machine is fully booted > up, results in a hardware accelerated device, so the cpu is not the > problem here. > Googling for this issue did not reveal something relevant nor did man > 4 aesni/man 8 geli, so here I am at the mailing list asking for > pointers. > Has anyone seen this behavior before? Do you have any hints? It looks like GEOM discovers your encrypted device before aesni module registers itself into opencrypto framework. If you want to experiment, you could try changing this line in sys/geom/geom.h: DECLARE_MODULE(name, name##_mod, SI_SUB_DRIVERS, SI_ORDER_FIRST); to something like this: DECLARE_MODULE(name, name##_mod, SI_SUB_DRIVERS, SI_ORDER_ANY); --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --DO5DiztRLs659m5i Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk+i3vkACgkQForvXbEpPzQxKgCgvn+aTY1sBJMqGXwJGNIviA2B GoYAniEmsJOVY4+tVhsNcRDlH8TY2xnE =+omN -----END PGP SIGNATURE----- --DO5DiztRLs659m5i--