Opened 10 years ago

Closed 10 years ago

Last modified 2 years ago

#1760 closed task (implemented)

Parallel Crypto: Design a good crypto parallelization plan and architecture

Reported by: nickm Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Blocker Keywords: tor-relay
Cc: Actual Points:
Parent ID: #1749 Points:
Reviewer: Sponsor:


Lest we repeat design mistakes of cryptography programs past ("Ready! Fire! Aim!"), we should really come up with a good design for how to split our crypto across multiple CPUs before we get too deeply involved in the coding.

This should at the very least include figuring out what new data structures we need, what new code we need, what runs in subthreads, and how to minimize the amount of calls from subthreads back to the main thread.

(It's okay for this to be threaded and not multiprocess, BTW: Everybody who matters besides OpenBSD has kernel threads nowadays.)

Child Tickets

Change History (7)

comment:1 Changed 10 years ago by nickm

I started writing up a design at

More work is needed.

comment:2 Changed 10 years ago by nickm

Resolution: implemented
Status: newclosed

More work was done; I am believing the current architecture.

comment:3 Changed 8 years ago by nickm

Keywords: tor-relay added

comment:4 Changed 8 years ago by nickm

Component: Tor RelayTor

comment:5 Changed 2 years ago by chelseakomlo

Severity: Blocker

This link to the design doc is no longer valid- mind re-linking?

comment:7 Changed 2 years ago by cypherpunks

Milestone: Deliverable-Sep2010
Note: See TracTickets for help on using tickets.