Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #9574

Closed (moved)
Open
Opened Aug 24, 2013 by Roger Dingledine@arma

Process ntor create cells before tap create cells?

Motivated by http://nsl.cs.columbia.edu/papers/2013/cellflood.raid13.pdf

A) In the attack case: If we're under attack by somebody flooding us with tap create cells, it would be nice if the ntor creates get processed before this flood. If this strategy forces them to flood us with ntor create cells instead, that raises the expense.

B) In the normal case: Since handling ntor create cells is faster than handling tap create cells anyway, we could get them out of the way earlier and improve performance even more for folks using ntor-based circuit handshakes.

We already prioritize create-fast cells in exactly this way, though implementation-wise it'll probably be different. For the implementation here, maybe we'll be happiest just keeping two onionskin queues, one for each type.

The only downside I can see is that it'll be harder to measure how much of a performance improvement we get from ntor creates, since now we speed it up in two ways that are hard to separate.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.4.x-final
Milestone
Tor: 0.2.4.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#9574