netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ken Savage <kens1835@shaw.ca>
To: netdev@vger.kernel.org
Subject: RED tc qdisc not dropping?
Date: Wed, 3 Oct 2012 14:14:50 -0600 (MDT)	[thread overview]
Message-ID: <986427880.11879793.1349295290592.JavaMail.root@cds046> (raw)
In-Reply-To: <1643425136.11868012.1349294650298.JavaMail.root@cds046>

Hi there,

I'm running openSUSE 12.2, using the machine as a router/WANsim device.

Previously, I was running an older CentOS installation with a 2.6 kernel,
and my tc-red commands ran just fine, and imposed some bandwidth constraint
to the packets upon egress.  In 3.4.6, this doesn't seem to be the case
any longer.

Without any restrictions, there would be 25-30Mbps of traffic flowing out
the interface -- this is to give you a sense of the data rate.


Now, this said, I did notice that the latest RED code has the 'harddrop'
option that I didn't have under CentOS with kernel 2.6.  So in my attempt
to see ANYTHING happening with 3.4.6, I entered:

tc qdisc add dev eth0 root red limit 40000 min 3000 max 9000 avpkt 1000 burst 5 harddrop probability 1


Issuing 'tc -s -d qdisc show dev eth0', I obtain:

qdisc red 8006: root refcnt 2 limit 40000b min 3000b max 9000b harddrop ewma 2 probability 0.73242 Scell_log 12
 Sent 254028472 bytes 207494 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  marked 0 early 0 pdrop 0 other 0


All those zeroes seem a little amiss to me  ;)


Any ideas?

Thanks,

Ken Savage
kens1835@shaw.ca

       reply	other threads:[~2012-10-03 20:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1643425136.11868012.1349294650298.JavaMail.root@cds046>
2012-10-03 20:14 ` Ken Savage [this message]
2012-10-03 21:12   ` RED tc qdisc not dropping? Eric Dumazet
2012-10-03 22:16     ` Ken Savage

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=986427880.11879793.1349295290592.JavaMail.root@cds046 \
    --to=kens1835@shaw.ca \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).