From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: dave taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Codel] [Bloat] better tc support for bittorrent/diffserv
Date: Mon, 14 May 2012 19:50:26 +0200 [thread overview]
Message-ID: <7imx5a3b4t.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <4FB129EC.90200@gmail.com> (dave taht's message of "Mon, 14 May 2012 08:51:08 -0700")
[Pro memoria, I'm the author of a few of the networking bits in
Transmission, notably the DHT, the µTP support and large parts of the
IPv6 code.]
> 0) No ecn on transmission, at least.
TCP flows will use ECN if your system is configured to use ECN. µTP
doesn't do ECN, and there's no easy way to implement it -- there's no
API to set ECN on UDP packets.
> Packets not marked as CS1,
Add
"peer-socket-tos": "lowcost",
to your settings.json.
> 1) The port number is consistent, but user-settable.
Only for µTP and incoming TCP. Outgoing TCP uses a random port.
It's a well known flaw of the sockets API that you cannot use the same
local port for incoming and outgoing connections.
> 4) Syntactically tc is missing some ip6 functionality, notably an
> orthogonal "tos" field to the ipv4 version.
Use ip6tables -j MARK.
-- Juliusz
next prev parent reply other threads:[~2012-05-14 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 15:51 [Codel] " dave taht
2012-05-14 17:50 ` Juliusz Chroboczek [this message]
2012-05-14 18:03 ` [Codel] [Bloat] " Eric Dumazet
2012-05-14 18:18 ` dave taht
2012-05-14 18:30 ` Juliusz Chroboczek
2012-05-14 18:35 ` dave taht
2012-05-14 18:24 ` Juliusz Chroboczek
2012-05-14 18:31 ` Eric Dumazet
2012-05-14 18:42 ` Eric Dumazet
2012-05-14 18:14 ` Dave Taht
2012-05-14 18:31 ` Juliusz Chroboczek
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7imx5a3b4t.fsf@lanthane.pps.jussieu.fr \
--to=jch@pps.jussieu.fr \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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