From: noreply@github.com
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat-iproute2] cbc435: Experimental SFQ flow, depth, head drop configurat...
Date: Fri, 6 Jan 2012 07:40:36 -0800 [thread overview]
Message-ID: <20120106154036.0673C427F3@smtp1.rs.github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat-iproute2
Commit: cbc435f542e798ba15b5f44fe273a7522e9c9c8c
https://github.com/dtaht/deBloat-iproute2/commit/cbc435f542e798ba15b5f44fe273a7522e9c9c8c
Author: Dave Taht <d@taht.net>
Date: 2012-01-06 (Fri, 06 Jan 2012)
Changed paths:
M include/linux/pkt_sched.h
M tc/q_sfq.c
Log Message:
-----------
Experimental SFQ flow, depth, head drop configuration support
The latest version of SFQ supports:
* Depth of queue
* flow limit of 65535
(Ability to have up to 65535 flows (instead of 127)))
* Ability to have a head drop (to drop old packets from a flow)
example of use : No more than 20 packets per flow, max 8000 flows, max
20000 packets in SFQ qdisc, hash table of 65536 slots.
tc qdisc add ... sfq \
flows 8000 \
depth 20 \
headdrop \
limit 20000 divisor 65536
Ram usage : 32 bytes per flow, instead of 384 for QFQ, so much better
cache hit ratio. 2 bytes per hash table slots, instead of 8 for QFQ.
reply other threads:[~2012-01-06 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120106154036.0673C427F3@smtp1.rs.github.com \
--to=noreply@github.com \
--cc=cerowrt-commits@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