From: Tom Eastep <teastep@shorewall.net>
To: "Nikolay S. Rybaloff" <nowhere@hakkenden.ath.cx>
Cc: Andrew Beverley <andy@andybev.com>, netfilter@vger.kernel.org
Subject: Re: Creating an equivalent to ESFQ using flow classifier
Date: Sun, 15 Mar 2009 11:53:15 -0700 [thread overview]
Message-ID: <49BD4E9B.8070100@shorewall.net> (raw)
In-Reply-To: <1237140472.28333.10.camel@hakkenden>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
Nikolay S. Rybaloff wrote:
>>
>> It is the last part that I am unsure about. I do not get any errors with
>> the commands, but they do not seem to make any difference to the shaping.
You are fortunate. Every time that I've tried to use the 'flow'
classifier with SFQ, the SFQ qdisc eventually drops 100% of the packets
presented to it.
Example:
tc qdisc add dev wlan0 root handle 1: sfq quantum 1514 limit 127
tc filter add dev wlan0 protocol ip pref 1 parent 1: handle 1 flow \
hash keys src,dst,proto-src divisor 1024
ursa:~ # tc -s qdisc ls dev wlan0
qdisc sfq 1: root limit 127p quantum 1514b
Sent 161724244 bytes 107284 pkt (dropped 200, overlimits 0 requeues 21313)
rate 0bit 0pps backlog 0b 0p requeues 21313
ursa:~ # tc -s qdisc ls dev wlan0
qdisc sfq 1: root limit 127p quantum 1514b
Sent 161724320 bytes 107285 pkt (dropped 205, overlimits 0 requeues 21313)
rate 0bit 0pps backlog 0b 0p requeues 21313
ursa:~ #
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-03-15 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 16:29 Creating an equivalent to ESFQ using flow classifier Andrew Beverley
2009-03-15 18:07 ` Nikolay S. Rybaloff
2009-03-15 18:53 ` Tom Eastep [this message]
2009-03-16 23:35 ` Andrew Beverley
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=49BD4E9B.8070100@shorewall.net \
--to=teastep@shorewall.net \
--cc=andy@andybev.com \
--cc=netfilter@vger.kernel.org \
--cc=nowhere@hakkenden.ath.cx \
/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