From owner-freebsd-current@FreeBSD.ORG Sat May 15 10:04:09 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC23F1065670; Sat, 15 May 2010 10:04:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 6238B8FC0A; Sat, 15 May 2010 10:04:08 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o4FA4FGV073611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 May 2010 13:04:15 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id o4FA42wv042472; Sat, 15 May 2010 13:04:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o4FA41Ij042471; Sat, 15 May 2010 13:04:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 15 May 2010 13:04:01 +0300 From: Kostik Belousov To: freebsd-current@freebsd.org Message-ID: <20100515100401.GT83316@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8bIXokQePRfDuBGo" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-amd64@freebsd.org Subject: AESNI driver and fpu_kern KPI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 May 2010 10:04:10 -0000 --8bIXokQePRfDuBGo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello, please find at http://people.freebsd.org/~kib/misc/aesni.1.patch the combined patch, containing the fpu_kern KPI and Intel AESNI crypto(9) driver. I did development and some testing on the hardware generously provided by Sentex Communications to Netperf cluster. I already posted the kern_fpu part. This is a KPI for x86 arches to denote the region of the kernel code as using the FPU/SSE hardware. I wanted to use the KPI for some in-kernel SSE code to have a proof that interface is useful and up to the task. The crypto(9) driver using AESNI instructions appeared to be a perfect match. Also, the patch should fix the "fpu dna in kernel mode" messages usually appearing when using VIA padlock engine. Padlock does not use FPU resources, but occasionally issues NPX exception if FPU is marked as unavailable due to context switch. I am interested in the problem reports and reviews. Maintainers of !x86-oids are welcome to provide feedback whether they feel that proposed KPI could be implemented on their architectures, or what modifications they consider as needed to be able to implement it. Unless major objections are raised or bugs are found, I plan to commit the fpu_kern KPI shortly. On the other hand, some code in the AESNI driver was derived from the Intel whitepaper, that does not specified a license for the code explicitely. I asked the author of the paper for clarification, he seems to be supportive. In the worst case, aeskeys_{i386,amd64}.S files would be rewritten from scratch. Until the issue is resolved, AESNI part cannot be committed. --8bIXokQePRfDuBGo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkvucZEACgkQC3+MBN1Mb4hm2gCg7bUL49W0EgcFJMsCtyjUI+x6 WzIAoKc/Pvey+o1xty4W5eGcyWCuohor =IPGe -----END PGP SIGNATURE----- --8bIXokQePRfDuBGo--