From owner-freebsd-arch@FreeBSD.ORG Mon Oct 21 18:32:15 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 21D3F4CE; Mon, 21 Oct 2013 18:32:15 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id DA26B2BD6; Mon, 21 Oct 2013 18:32:14 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 8F74F3EB4A; Mon, 21 Oct 2013 18:32:13 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.7/8.14.7) with ESMTP id r9LIWDRx037749; Mon, 21 Oct 2013 18:32:13 GMT (envelope-from phk@phk.freebsd.dk) To: John-Mark Gurney Subject: Re: always load aesni or load it when cpu supports it In-reply-to: <20131021182834.GX56872@funkthat.com> From: "Poul-Henning Kamp" References: <20131020070022.GP56872@funkthat.com> <423D921D-6CE5-49D9-BCED-AB14EB236800@grondar.org> <20131020161634.GQ56872@funkthat.com> <5264F074.4010607@freebsd.org> <20131021164034.GU56872@funkthat.com> <37693.1382379728@critter.freebsd.dk> <20131021182834.GX56872@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1 Date: Mon, 21 Oct 2013 18:32:13 +0000 Message-ID: <37748.1382380333@critter.freebsd.dk> Cc: Andre Oppermann , Mark R V Murray , freebsd-arch@freebsd.org 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: Mon, 21 Oct 2013 18:32:15 -0000 In message <20131021182834.GX56872@funkthat.com>, John-Mark Gurney writes: >If you're on a slow system (embeded x86 or arm) that has an AES >accelerator, you really want to be using your accelerator than wasting >your cpu cycles on large blockes of AES... First, as I said in my previous email: I have still to see "distant" crypto accelerator do any good if you have idle CPU, even on a soekris 4801. If you have a real-life benchmark showing that, I'd like to see it. Second, if you want a limit, at the very least it should be MAXPHYS. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.