From owner-freebsd-geom@FreeBSD.ORG Sun Apr 29 02:46:49 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 0BFD6106564A for ; Sun, 29 Apr 2012 02:46:49 +0000 (UTC) (envelope-from vrachil@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 93E098FC0C for ; Sun, 29 Apr 2012 02:46:48 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so1784953wgb.31 for ; Sat, 28 Apr 2012 19:46:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=TJU8Y93d+tMt/MSjJ9htypTBuMEXQQ1IRI35XGOSF7s=; b=mBMBjNsVDNfkW6vX7MRMuJS9KYLxFRRClVXRPBZ7WJGk11RvjOtBnKPKzwFQSANYVP 2AYZuKQAMNUyMg8BfRlRGrVYJt64416xKTd9PEnGAS0xVfgk95hWjqlbtfZ5hRh7bSRg dO6RMwZKCK4k4Z4pBf0SAV1w9JI86oAVwZAzr1+2kotrZIFeKuCq0Q9M7LtlEYrn4DQs yCitNyMj/aQMcDKzTX628ffJHb9mXOTUga2qny26QRId4YP8d2qlWbASfchYLLkDBP5+ Y8MsG9oFeofJX5RlUdv1zOli2snoaRgPL4hWwHGa3Y3unPoKjDyAzpFwvZW2J/js41Lr EL6g== Received: by 10.180.92.130 with SMTP id cm2mr10510933wib.4.1335667607554; Sat, 28 Apr 2012 19:46:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.179.199 with HTTP; Sat, 28 Apr 2012 19:46:27 -0700 (PDT) From: Ilias-Dimitrios Vrachnis Date: Sun, 29 Apr 2012 05:46:27 +0300 Message-ID: To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: 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: Sun, 29 Apr 2012 02:46:49 -0000 Hello, I have a question about the aesni integration with geli: 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. 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? PS. I'm running -CURRENT (r234772)