From: Dave Taht <dave@taht.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Adding congestion control to the Tor network
Date: Tue, 04 Feb 2020 12:21:43 -0800 [thread overview]
Message-ID: <877e12w1bc.fsf@taht.net> (raw)
In-Reply-To: <871rra62z8.fsf@toke.dk> ("Toke \=\?utf-8\?Q\?H\=C3\=B8iland-J\?\= \=\?utf-8\?Q\?\=C3\=B8rgensen\=22's\?\= message of "Tue, 04 Feb 2020 11:50:19 +0100")
I'm looking forward to their upcoming netdevconf talk:
https://netdevconf.info/0x14/session.html?talk-reducing-kernel-queuing-delays-with-TCP-window-space-events
There are a metric ton of network and congestion control related talks at
this conference in this go-round. Some ideas seem brilliant, others,
brain damaged.
Toke Høiland-Jørgensen <toke@toke.dk> writes:
> I figured that this lengthy overview of past and future attempts at
> adding congestion control to the Tor network might be interesting to
> people here:
>
> https://lists.torproject.org/pipermail/tor-dev/2020-January/014140.html
That was reallly good, thank you. Heavy on ECN derived
ideas... fq_codel/pie not in there...
Once again FQ gets a bit of short shrift, given that only a few fat
flows need congestion control to kick in relative to the others. Of
course I have no idea from the regularity of classic FQ how that yields
to traffic analysis in one way or another, but I do certainly hope they
are mixing up traffic as much as possible within a cell?
I've generally found tor to be pretty unusable for my impatient self.
The last time I paid attention was in this: http://www.cypherpunks.ca/~iang/pubs/defenestrator.pdf
which is also referenced in the above discussion.
>
> -Toke
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2020-02-04 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 10:50 Toke Høiland-Jørgensen
2020-02-04 20:21 ` Dave Taht [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e12w1bc.fsf@taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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