Re: TLS, threads, and workers

To: or-dev@freehaven.net
Subject: Re: TLS, threads, and workers
From: "Joel N. Weber II" <ordev@joelweber.com>
Date: Sun, 07 Sep 2003 13:38:01 -0400
Delivered-to: archiver@seul.org
Delivered-to: or-dev-outgoing@seul.org
Delivered-to: or-dev@seul.org
Delivery-date: Sun, 07 Sep 2003 13:38:39 -0400
In-reply-to: <20030905212608.X7514@moria.mit.edu> (message from RogerDingledine on Fri, 5 Sep 2003 21:26:08 -0400)
References: <20030904032335.S7514@moria.mit.edu> <20030904162015.GD645@itd.nrl.navy.mil> <1062708947.1256.85.camel@totoro.wangafu.net> <3F58C654.4010702@algroup.co.uk> <20030905212608.X7514@moria.mit.edu>
Reply-to: or-dev@freehaven.net
Sender: owner-or-dev@freehaven.net

It seems like the obvious thing to do is limit the number of new TLS
connections you bother to try to process in a given amount of time.

References:
- TLS, threads, and workers
  - From: Roger Dingledine <arma@mit.edu>
- Re: TLS, threads, and workers
  - From: Paul Syverson <syverson@itd.nrl.navy.mil>
- Re: TLS, threads, and workers
  - From: Nick Mathewson <nickm@alum.mit.edu>
- Re: TLS, threads, and workers
  - From: Ben Laurie <ben@algroup.co.uk>
- Re: TLS, threads, and workers
  - From: Roger Dingledine <arma@mit.edu>