From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.jussieu.fr>
Cc: codel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Codel] [Bloat] better tc support for bittorrent/diffserv
Date: Mon, 14 May 2012 11:14:02 -0700 [thread overview]
Message-ID: <CAA93jw5wT=p=OZjn0ZOTxfte48M32MN056vBd0KA+TB8W9XcJQ@mail.gmail.com> (raw)
In-Reply-To: <7imx5a3b4t.fsf@lanthane.pps.jussieu.fr>
On Mon, May 14, 2012 at 10:50 AM, Juliusz Chroboczek <jch@pps.jussieu.fr> wrote:
>
>> 4) Syntactically tc is missing some ip6 functionality, notably an
>> orthogonal "tos" field to the ipv4 version.
>
> Use ip6tables -j MARK.
ip6tables...
Doesn't work on ingress presently, if you are using ifb (I can be wrong).
Using something to lightly shape the last hop (host) incoming packets, like
htb set to a very large fraction of the card's bandwidth and codel set to
a target of 500us delay on ingress, seems to work.
With egress and ingress rate limiting on I can get delay for large numbers
of flows in both directions in a saturated situation down to < 5ms with
fq_codel in place attached to htb.
Best of all, if you have ecn enabled on that host and the packets are marked
3 on ingress in that scenario, you don't drop anything on that last hop...
>
> -- Juliusz
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
next prev parent reply other threads:[~2012-05-14 18:14 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 ` [Codel] [Bloat] " Juliusz Chroboczek
2012-05-14 18:03 ` 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 [this message]
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='CAA93jw5wT=p=OZjn0ZOTxfte48M32MN056vBd0KA+TB8W9XcJQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=jch@pps.jussieu.fr \
/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