Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #2799

Closed (moved)
(moved)
Open
Created Mar 25, 2011 by Nick Mathewson@nickm🏃

Use cbt results when deciding to launch parallel introduction circuit?

Right now, circuituse.c has this lovely snippet in circuit_get_best:


/* XXX022 make this 15 be a function of circuit finishing times we've
 * seen lately, a la Fallon Chen's GSoC work -RD */
#define REND_PARALLEL_INTRO_DELAY 15
    if (purpose == CIRCUIT_PURPOSE_C_INTRODUCE_ACK_WAIT &&
             !must_be_open && circ->state != CIRCUIT_STATE_OPEN &&
             circ->timestamp_created + REND_PARALLEL_INTRO_DELAY < now) {
      intro_going_on_but_too_old = 1;
      continue;
    }

Now that we've got our circ_times stuff, we can totally get a better estimate of "that time after which we should launch another introduction circuit but still give this one time to finish." Yes?

Parenthetically, I have no idea what "!must_be_open" is doing there.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking