[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Path-spec - fast circuits
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Path-spec - fast circuits
- From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
- Date: Fri, 12 Feb 2010 22:46:18 -0500
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Fri, 12 Feb 2010 22:46:26 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Yjtbv+PJifJWFrmqOM7dGuNrbcDgC8/SB+N7xI9NHC8=; b=kuTWJceGfk1fliQwk32E/SCi3wMJ8gtNOdg5fRRqInkfcuaIPHlEKwPhDnNdnbxl0B KmYcCjsafGWvNARRVpGbOriJ1wVDm2oO3PDDgC2CaYTAapEPIeUeAIHg8ktkUiLBaMCL JrmEXPBaLohVow6d7xbs3u8OmTMiGsXcYHPWQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=twppFu8KUzYvAcSXfFQvQiPYvyJgH1IPWYxhfcOeR8+PzCCXccELqeRnkULOo3qquC kInrekZigmlPh32gUhdc3ba/cLq2HFJD2pMz+ImIehX2UQbd6rFbIRhIV7odk6iTCleA DYwOzMGI7YNIrpH1KcLGFYvFY6Hlub9XVfesc=
- In-reply-to: <5bfb757a1002120159r574bdacyc00786641dece7f8@xxxxxxxxxxxxxx>
- References: <5bfb757a1002120159r574bdacyc00786641dece7f8@xxxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
2010/2/12 ilter yüksel <ilteryuksel@xxxxxxxxx>:
> Hello,
>
> For exit router selection path-spec says that;
>
> "For circuits that do not need to be "fast", when choosing among multiple
> candidates for a path element, we choose randomly. For "fast" circuits, we
> pick a given router as an exit with probability proportional to its
> bandwidth."
>
> Could anybody explain why Tor pick exit router with probability proportional
> to its bandwidth only for fast circuits? As far as i know Tor uses this
> technique for load-balance. But why it uses this technique only for fast
> circuits?
First of all, "Fast" circuits are a bit misnamed as used in
path-spec.txt. Basically, "fast" means "bandwidth-sensitive". The
only ones that aren't don't need to be "fast" in this sense are ones
that are going to be used only for a tiny amount of traffic.
That said, I think the statement in path-spec.txt may be poor. It
probably makes sense to weight all choices by bandwidth, now that
bandwidth is measured rather than just being self-advertised.
To see what the code is actually doing, the string to search for is
need_capacity or NEED_CAPACITY. The most interesting layer to look
for this is at is where it's passed as a flag to
circuit_launch_by_router() or circuit_launch_by_extend_info().
--
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/