From owner-freebsd-arch@FreeBSD.ORG Sun Oct 20 07:00:24 2013 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 83E1C548 for ; Sun, 20 Oct 2013 07:00:24 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 67DAF2941 for ; Sun, 20 Oct 2013 07:00:23 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r9K70Mi6024675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 20 Oct 2013 00:00:23 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r9K70MjL024674 for freebsd-arch@FreeBSD.org; Sun, 20 Oct 2013 00:00:22 -0700 (PDT) (envelope-from jmg) Date: Sun, 20 Oct 2013 00:00:22 -0700 From: John-Mark Gurney To: freebsd-arch@FreeBSD.org Subject: always load aesni or load it when cpu supports it Message-ID: <20131020070022.GP56872@funkthat.com> Mail-Followup-To: freebsd-arch@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Sun, 20 Oct 2013 00:00:23 -0700 (PDT) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Oct 2013 07:00:24 -0000 So, I'd like to get aesni more widely used. I didn't even realize one of my AMD cpus even supported AES-NI till I decided to look at the caps and realized it did. If we had been loading the AES-NI module, I would have realized it sooner. So, should we now add it to GENERIC? or should we (and by we, I mean I) add code to loader to load it when the cpu supports it? Yes, the aesni module is small, but dynamicly loading it would allow us to continue to keep the kernel small, and this could possibly be used as a framework for other modules too. Comments? Suggestions or ideas? Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."