Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Laurent Haond <lhaond@bearstech.com>
To: lartc@vger.kernel.org
Subject: [LARTC] tc qdisc ingress problem ?
Date: Thu, 26 Jan 2006 10:33:12 +0000	[thread overview]
Message-ID: <43D8A568.8040202@bearstech.com> (raw)

Hi, all

I've got problems with tc qdisc ingress.
I'm using vanillia kernel 2.6.14.4 patched with
http://www.ssi.bg/~ja/routes-2.6.14-12.diff, and iproute2-2.6.14-051107.

i am using ingress to limit incoming traffic :
(DEV is eth1 /  DOWNLINK is 7700)

# attach ingress policer:
tc qdisc add dev $DEV handle ffff: ingress

# filter *everything* to it (0.0.0.0/0), drop everything that's
# coming in too fast:
tc filter add dev $DEV parent ffff: protocol ip prio 50 u32 match ip src \lm
   0.0.0.0/0 police rate ${DOWNLINK}kbit burst 10k drop flowid :1

This does limit traffic but to ~32KB/s !!

#tc -s qdisc show dev eth1
[...]
qdisc ingress ffff: ----------------
 Sent 37001411 bytes 51120 pkt (dropped 3422, overlimits 0 requeues 0)
 rate 0bit 0pps backlog 0b 0p requeues 0

It's is normal to have dropped packets without overlimits ??

Could it be related to CPU performance (overload), i'm using a wrap2
board (geode sc1100 at 266Mhz) ?
Running top during a big download, it appears that cpu is 95% idle...

Thanks

Laurent Haond

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2006-01-26 10:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 10:33 Laurent Haond [this message]
2006-01-30 11:55 ` [LARTC] tc qdisc ingress problem ? Laurent Haond

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=43D8A568.8040202@bearstech.com \
    --to=lhaond@bearstech.com \
    --cc=lartc@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