Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Putting cake under dsmark on ingress ifb
Date: Sun, 26 Feb 2017 13:41:33 +0000	[thread overview]
Message-ID: <ee77f363-cbcb-f0f1-a8a3-b3409eaaa120@gmail.com> (raw)

I am well rusty with linux qos and have never tried dsmark before.

I am likely doing something stupid here :-)

So the test: I want to set dsmark on ingress traffic so I can control
which cake tin it goes to - test just marking icmp as ef.

ingress qdisc is added to ppp0 and redirected to ifb0, on which I do -

tc qdisc add dev ifb0 handle 1:0 root dsmark indices 64

tc filter add dev ifb0 parent 1:0 protocol ip prio 1 u32 match ip 
protocol 1 0xff classid 1:1

tc class change dev ifb0 classid 1:1 dsmark mask 0x3 value 0xb8

This works in the sense that I can now get tcpdump on a PC on the
lan to show incoming icmp with tos 0xb8.

So I try to add cake under dsmark ini the hope that it sees icmp as ef
but it doesn't, icmp goes to best effort.

tc qdisc add dev ifb0 handle 2:0 parent 1:0 cake bandwidth 60mbit raw 
overhead 34 diffserv4

tc -s -d qdisc  ls dev ifb0
qdisc dsmark 1: root refcnt 2 indices 0x0040
  Sent 60259205 bytes 71562 pkt (dropped 8, overlimits 0 requeues 0)
  backlog 0b 0p requeues 0
qdisc cake 2: parent 1: bandwidth 60Mbit diffserv4 triple-isolate rtt 
100.0ms noatm overhead 48 via-ethernet
  Sent 60254313 bytes 71495 pkt (dropped 8, overlimits 67924 requeues 0)
  backlog 0b 0p requeues 0
  memory used: 160448b of 4Mb
  capacity estimate: 60Mbit
                  Bulk   Best Effort      Video       Voice
   thresh      3750Kbit      60Mbit      30Mbit      15Mbit
   target         5.0ms       5.0ms       5.0ms       5.0ms
   interval     100.0ms     100.0ms     100.0ms     100.0ms
   pk_delay         4us       311us        87us         7us
   av_delay         0us       214us         4us         0us
   sp_delay         0us         6us         4us         0us
   pkts               3       71367          95          38
   bytes            124    60246264       18265        1554
   way_inds           0         182           0           0
   way_miss           3        7043          77           7
   way_cols           0           0           0           0
   drops              0           8           0           0
   marks              0           0           0           0
   sp_flows           0           1           0           0
   bk_flows           0           0           0           0
   un_flows           0           0           0           0
   max_len           44        1500        1151          78

The packets showing as voice are AFAIKT ntp. pinging from lan
still shows 0xb8 but the counters show that they are going through
Best Effort.

Anyone see what's wrong?

TIA.

             reply	other threads:[~2017-02-26 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 13:41 Andy Furniss [this message]
2017-02-26 13:47 ` Jonathan Morton
2017-02-26 14:30   ` Andy Furniss
2017-02-28 14:11     ` Andy Furniss
2017-02-28 14:23       ` Jonathan Morton
2017-03-01 23:14       ` Andy Furniss
2017-03-04 17:43         ` Andy Furniss

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=ee77f363-cbcb-f0f1-a8a3-b3409eaaa120@gmail.com \
    --to=adf.lists@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    /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