From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 11 09:57:02 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CD82106566C for ; Sun, 11 Mar 2012 09:57:02 +0000 (UTC) (envelope-from ol@csa.ru) Received: from srv.oltel.org (skynet.oltel.org [93.100.48.130]) by mx1.freebsd.org (Postfix) with ESMTP id B9DF48FC14 for ; Sun, 11 Mar 2012 09:57:01 +0000 (UTC) Received: by srv.oltel.org (Postfix, from userid 110) id CBA5C153424; Sun, 11 Mar 2012 13:49:30 +0400 (MSK) X-Virus-Scanned: amavisd-new at csa.ru Received: from srv.oltel.org ([127.0.0.1]) by srv.oltel.org (mail.csa.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id akvr7hDCuk3B; Sun, 11 Mar 2012 13:49:27 +0400 (MSK) Received: from [192.168.103.127] (unknown [192.168.103.127]) by srv.oltel.org (Postfix) with ESMTPSA id 59C03153421; Sun, 11 Mar 2012 13:49:27 +0400 (MSK) Message-ID: <4F5C7527.9000609@csa.ru> Date: Sun, 11 Mar 2012 13:49:27 +0400 From: Oleg Baranov User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19 MIME-Version: 1.0 To: =?UTF-8?B?5Zu+5r2Y?= References: <4F2D2293.5050108@gurgelmail.com> <1331325651390-5551674.post@n5.nabble.com> <4F5B10B4.9020300@csa.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hardware@freebsd.org Subject: Re: AMD Bulldozer and aesni driver X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Mar 2012 09:57:02 -0000 Hi! I mean that most of software which utilizes encryption relies on OpenSSL library. It looks that current version of OpenSSL in FreeBSD cannot use aesni as hardware accelerator, so all that software cannot benefit from using aesni. On the other hand there is stuff like ipsec and geli which relies on crypto(9) framework. This may use aesni accelerator. Unfortunately the machine with Bulldozer that I have use neither of them so I cannot tell how significant improvement is. On 03/10/2012 07:36 PM, 图潘 wrote: > What patches are you talking about? There is an official aesni driver > http://www.freebsd.org/cgi/man.cgi?query=aesni&sektion=4&manpath=FreeBSD+8.2-RELEASE > And it does work for intel. > Sorry I didnt quite understand you fully. Do you mean it does not work > in general? > > > On Sat, Mar 10, 2012 at 9:28 AM, Oleg Baranov wrote: >> Hi! >> >> aesni(4) driver detects the module on Bulldozer fine. >> I was happy to see it first but then I found out that openssl that goes as >> part of FreeBSD distribution lacks AESNI engine module. >> There are some patches for bringing aesni into FreeBSD mentioned on forums >> but this in not a production-system-running approach for me. >> So the answer is YES - it exists, but right then NO - it does not work. >> >> >> >> CPU: AMD FX(tm)-8120 Eight-Core Processor (3110.48-MHz K8-class >> CPU) >> Origin = "AuthenticAMD" Id = 0x600f12 Family = 15 Model = 1 Stepping = >> 2 >> Features=0x178bfbff >> Features2=0x1698220b >> AMD Features=0x2e500800 >> AMD >> Features2=0x1c9bfff,> >> TSC: P-state invariant, performance statistics >> real memory = 17179869184 (16384 MB) >> avail memory = 16460046336 (15697 MB) >> Event timer "LAPIC" quality 400 >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs >> FreeBSD/SMP: 1 package(s) x 8 core(s) >> cpu0 (BSP): APIC ID: 16 >> cpu1 (AP): APIC ID: 17 >> cpu2 (AP): APIC ID: 18 >> cpu3 (AP): APIC ID: 19 >> cpu4 (AP): APIC ID: 20 >> cpu5 (AP): APIC ID: 21 >> cpu6 (AP): APIC ID: 22 >> cpu7 (AP): APIC ID: 23 >> ACPI Warning: Optional field Pm2ControlBlock has zero address or length: >> 0x0000000000000000/0x1 (20110527/tbfadt-586) >> ioapic0 irqs 0-23 on motherboard >> ioapic1 irqs 24-55 on motherboard >> kbd1 at kbdmux0 >> cryptosoft0: on motherboard >> aesni0: on motherboard >> >> >> >> >> >> On 03/10/2012 12:40 AM, 潘图 wrote: >>> Still no info on this? >>> I am also about to buy a bulldozer, but I need to know if the aesni driver >>> supports the bulldozer. >>> Please anyone already using it? >>