From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] flow_hash vs host_hash
Date: Tue, 06 Oct 2015 10:28:32 +0200 [thread overview]
Message-ID: <87fv1o2yfj.fsf@toke.dk> (raw)
In-Reply-To: <A31A0F3B-88F7-4A11-8BDC-9DEC2F336999@gmx.de> (Sebastian Moeller's message of "Tue, 6 Oct 2015 10:27:26 +0200")
Sebastian Moeller <moeller0@gmx.de> writes:
> Hi Toke,
>
> On Oct 6, 2015, at 10:13 , Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>> Sebastian Moeller <moeller0@gmx.de> writes:
>>
>>> I believe you nailed it, but the pony will still work on egress,
>>
>> Don't packets hit the qdisc after NAT has been applied?
>
> As far as I know not for IFBs; that is the reason why we need tc filters
> on ingress and can not use netfilter. And why using iptables to map the DSCP to
> zero will still result in our shaper seeing the DSCP markings from upstream
> (which I could confirm happening for IPv6, as my ISP conserved flent’s DSCP
> marks, so I saw nice priority band based stratification in flent's graphics). I
> think that IFBs predecessor IMQ was different in that regard.
No, I meant on egress...
-Toke
next prev parent reply other threads:[~2015-10-06 8:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 12:20 Dave Taht
2015-10-05 12:30 ` Jonathan Morton
2015-10-05 12:45 ` Sebastian Moeller
2015-10-05 14:01 ` Dave Taht
2015-10-06 6:26 ` Kevin Darbyshire-Bryant
2015-10-06 7:18 ` Sebastian Moeller
2015-10-06 8:13 ` Toke Høiland-Jørgensen
2015-10-06 8:27 ` Sebastian Moeller
2015-10-06 8:28 ` Toke Høiland-Jørgensen [this message]
2015-10-06 8:37 ` Sebastian Moeller
2015-10-06 8:39 ` Toke Høiland-Jørgensen
2015-10-06 8:44 ` Jonathan Morton
2015-10-06 10:59 ` Sebastian Moeller
2015-10-06 12:51 ` Dave Taht
2015-10-06 13:56 ` Jonathan Morton
2015-10-06 15:07 ` David Lang
2015-10-06 9:38 ` Sebastian Moeller
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fv1o2yfj.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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