Delivery-Date: Tue, 11 Aug 2015 19:33:02 -0400
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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	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 B4C8B1E0507;
	Tue, 11 Aug 2015 19:33:00 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DC9F833FEC;
	Tue, 11 Aug 2015 23:32:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id EF42E33F8F
 for <tor-talk@lists.torproject.org>; Tue, 11 Aug 2015 23:32:52 +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 A_4NY-YDXdwN for <tor-talk@lists.torproject.org>;
 Tue, 11 Aug 2015 23:32:52 +0000 (UTC)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com
 [IPv6:2a00:1450:4010:c03::22c])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 91E0333F15
 for <tor-talk@lists.torproject.org>; Tue, 11 Aug 2015 23:32:52 +0000 (UTC)
Received: by labd1 with SMTP id d1so365651lab.1
 for <tor-talk@lists.torproject.org>; Tue, 11 Aug 2015 16:32:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=1l1evcZdmuYL1XmUUbWWsA5rbICY3XZw8IxhN7ttVvU=;
 b=Z6Xbx5uf9NJl2Dieyf1o7ymHux8PmNNSvgzmtbddujh0jAAWhqe+UMirvi4CDnokLv
 uRqLKENm7b8qqqRPc73JAnqmQIYtVtX/kdEllcYAKUrgXaBF3dn/0mIpxBHT8wdY6I5Y
 D0edPNs7ziqKFVs90GNA1eqKIuzhgu3PALlKiNTsQmVt8NWv1xM8I4iWLOB9IGhTlRyr
 B+ixZZyqg0rm4mszpDB9YZhNqGqWejddnBOWwDs5jXSJeTtAbV8uP/xt6wyaBbCeTOvT
 spPPIszHpuSkRRzYBcG+xGWd6xR7R/hQ88QfXw744uqUU/hOL+EHhK6OCl/IWyvEaUt8
 ZW3A==
MIME-Version: 1.0
X-Received: by 10.112.13.166 with SMTP id i6mr29573254lbc.50.1439335969439;
 Tue, 11 Aug 2015 16:32:49 -0700 (PDT)
Received: by 10.25.91.206 with HTTP; Tue, 11 Aug 2015 16:32:49 -0700 (PDT)
In-Reply-To: <20150812034223.3dff7080@natsu>
References: <CAO7N=i1fRB5cx6Z0=vLwj9_CykuPAk=NBiV=6q=FX5tD5qX2jQ@mail.gmail.com>
 <55CA76F1.4030206@rawbw.com> <20150812034223.3dff7080@natsu>
Date: Tue, 11 Aug 2015 16:32:49 -0700
Message-ID: <CAJVRA1QaksmhxvVBYzJyzoLcr8txTEYEf5NNS-uXDMaLmghaDw@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] (no subject)
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>

On 8/11/15, Roman Mamedov <rm@romanrm.net> wrote:
> ...
> *Repeatedly headbangs on the desk*
>
> Uhm so what was I talking about. Ah yes, I believe that's not the case. It
> would add a great deal of benefit actually.

it would be useful, particularly on systems with native acceleration
of supported crypto primitives.



> As to why it's not implemented, I think simply because no one has coded it
> yet.

correct. in particular, making the Tor internals efficiently
multi-threaded is difficult due to the particulars of crypto and Tor
network I/O in the implementation.

i thought i had a list of Trac tickets to the gist of this matter,
  alas i cannot find them. perhaps someone else has a convenient collection?

this also came up in context of using CUDA or OpenCL to accelerate
network crypto via CPU offload to GPU.

the good news is that it is maybe less hard now, than it was some
years ago, to make this transition to well threaded internals in Tor.
maybe soon, even closer yet. and as you mention, patches welcome since
the best fix is code under test :)


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

