From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: ju@klipix.org, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] fq_codel through Tor
Date: Sat, 19 Jan 2013 01:17:12 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1301190115020.2151@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw6uTnht1sB9VhB-UXuBgrJSQ97yj0wdNGQU7JmtwrL__g@mail.gmail.com>
[-- Attachment #1: Type: TEXT/Plain, Size: 614 bytes --]
On Sat, 19 Jan 2013, Dave Taht wrote:
> https://srv1.openwireless.org/pipermail/tech/2012-December/000332.html
>
> I haven't the foggiest idea what this traffic would look like. Is it even
> possible to induce bufferbloat through tor?
with your packets bouncing through so many systems there are sure a lot of
buffers in play. Especially given that Tor is not trying to find the most
efficent route to send the packets, I would not be surprised to see occasional
bottlenecks.
On the other hand, I don't know what you can do other than the basic queue
management stuff you are already working on.
David Lang
[-- Attachment #2: Type: TEXT/PLAIN, Size: 164 bytes --]
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2013-01-19 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 7:18 Dave Taht
2013-01-19 9:17 ` David Lang [this message]
2013-01-19 10:03 ` Maciej Soltysiak
2013-01-19 13:39 ` dpreed
2013-01-19 16:42 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1301190115020.2151@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=ju@klipix.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox