Delivery-Date: Sat, 03 Jan 2015 04:40:42 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 0F2421E030B
	for <archiver@seul.org>; Sat,  3 Jan 2015 04:40:41 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3629832A55;
	Sat,  3 Jan 2015 09:40:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3E850327D8;
 Sat,  3 Jan 2015 09:40:32 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Rvh2qDIlLigO; Sat,  3 Jan 2015 09:40:32 +0000 (UTC)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com
 [IPv6:2607:f8b0:4001:c05::22e])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 1A5FB3256E;
 Sat,  3 Jan 2015 09:40:32 +0000 (UTC)
Received: by mail-ig0-f174.google.com with SMTP id hn15so531895igb.13;
 Sat, 03 Jan 2015 01:40:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:from:date:message-id:subject:to:content-type;
 bh=b1fEvVQ25pgJFxYh3nhOfNKQFVK802eQ562fcm7BVY4=;
 b=pxC6mDTK0DzqOltq9d1yzdFk2GdE2VSfBYUIefhJWfWaIaNNlXZ4utnMnjnic9awE5
 8gXxl8YL8/BZgOfCxS4aKWm5F5v+s8abbqDee74R5sglIoTv4oZOkPWmoa9y2CQ1oQL0
 pvsJCTrCUZK0NnDhW+VIPsDOub4c+YQGL38syhcmyJwUGitLU50EHiNecGcmRo7z+kMW
 yVXLp8lRjuK6N+XlBMlrckEja8U9G9H17akyg3UaPUHzQ+tZ9JOZ2R4CTMXjlxZ3lidg
 KyDgVvNO3Qzt0IHThBAQeaUTPeXnAJeaT6LQIuxDDISUD232Ed2I31McxuQqTLdbFe/H
 NdNg==
X-Received: by 10.107.154.198 with SMTP id c189mr72579994ioe.68.1420278029831; 
 Sat, 03 Jan 2015 01:40:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.167.6 with HTTP; Sat, 3 Jan 2015 01:39:49 -0800 (PST)
From: usprey <usprey@gmail.com>
Date: Sat, 3 Jan 2015 10:39:49 +0100
X-Google-Sender-Auth: FMnPqZWNYHnfrDdmyaLRw6E_4lI
Message-ID: <CAOmikWHB8yhfvHNh0ZW-d51zKbswZ_-6awgFvLR0dEB+OKvOBA@mail.gmail.com>
To: tor-talk@lists.torproject.org, tor-relays@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] HardwareAccel: Current proper use???
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Summary:
The documentation is still somewhat vague on the best use of the
"HardwareAccel" option.

> *HardwareAccel* *0*|*1*
>
> If non-zero, try to use built-in (static) crypto hardware acceleration
> when available. (Default: 0)
>
I could not find a definitive answer in the archives or in
https://gitweb.torproject.org/tor.git/log/?qt=grep&q=hardwareaccel&showmsg=1
.

https://www.torservers.net/wiki/setup/server#aes-ni_crypto_acceleration claims
no intervention is needed in regards of aes-ni accelaration, but I would
like to add an explanation or source to this recommendation.

Question_1:
If my CPU supports and have loaded aesni_intel on linux with OpenSSL is
1.0.1.j-1, should I leave HardwareAccel off or explicitly enable it?

Question_2:
What does "*built-in (static) crypto hardware acceleration*" refer to?
Dedicated hardware, CPU-support or...?

Best regards
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

