From: Sebastian Moeller <moeller0@gmx.de>
To: Y <intruder_tkyf@yahoo.fr>,cake@lists.bufferbloat.net
Subject: Re: [Cake] diffserv based on firewall mark
Date: Wed, 12 Oct 2016 21:59:39 +0200 [thread overview]
Message-ID: <0CF95236-FA9B-4139-B38B-FB7D941B797F@gmx.de> (raw)
In-Reply-To: <20161013044247.24787477cda163a9b40d2ea8@yahoo.fr>
Hi yuta,
It would maybe be more convincing if you could share data showing how ack priority would help cake. I know that it has long been recommended, but I am missing recent data showing that it still would work for cake and fq_codel, as these tend to boost all sparse flows, and ack flows often are sparse... But feel free to ignore me, I am not advancing cake's development.
Best Regards
Sebastian
On October 12, 2016 9:42:47 PM GMT+02:00, Y <intruder_tkyf@yahoo.fr> wrote:
>Hi , I am yuta.
>
>I request to add TCP ACK priority first.
>
>Bye Bye.
>
>On Wed, 12 Oct 2016 13:52:14 +0800
>ching lu <lsching17@gmail.com> wrote:
>
>> My current config is HTB+fq-codel.
>>
>> I deprioritize bittorrent traffic by marking related connections in
>> iptables (e.g. detect by port number) and route them to corresponding
>> HTB class and qdisc.
>>
>> How can i archive the same goal using the cake qdisc?
>>
>> I am aware that cake supports Diffserv by DSCP, but i think it is not
>applicable
>>
>> 1. i do not know to turn on DSCP for Winodws 8 (or above) client <-
>> someone may know
>> 2. ingress traffic do not have DSCP
>>
>>
>> Thanks in advance
>> _______________________________________________
>> Cake mailing list
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
>
>
>--
>Y <intruder_tkyf@yahoo.fr>
>_______________________________________________
>Cake mailing list
>Cake@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cake
prev parent reply other threads:[~2016-10-12 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 5:52 ching lu
2016-10-12 7:26 ` Jonathan Morton
2016-10-12 8:11 ` ching lu
2016-10-12 9:10 ` moeller0
2016-10-12 9:35 ` ching lu
2016-10-12 10:05 ` moeller0
[not found] ` <CACHiF8D=iF4cww0QRC-UODpvC=oRmchP6jp3tT2A-=9M2piy+g@mail.gmail.com>
[not found] ` <CACHiF8BH2Pfx7de8Se6pv83tHUx1enLt_pc1MBp=uSs2mD=kYA@mail.gmail.com>
2016-10-12 10:17 ` ching lu
2016-10-12 10:21 ` Dave Taht
2016-10-12 11:10 ` Kevin Darbyshire-Bryant
2016-10-12 12:07 ` moeller0
2016-10-12 12:04 ` moeller0
2016-10-12 12:40 ` ching lu
2016-10-12 13:07 ` moeller0
2016-10-13 0:08 ` ching lu
2016-10-12 15:36 ` Jonathan Morton
2016-10-12 20:19 ` Sebastian Moeller
2016-10-13 0:19 ` ching lu
2016-10-13 0:26 ` David Lang
2016-10-12 19:42 ` Y
2016-10-12 19:59 ` Sebastian Moeller [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/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=0CF95236-FA9B-4139-B38B-FB7D941B797F@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=intruder_tkyf@yahoo.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