From: Michal Soltys <nozo@ziu.info>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] using tc to drop packets based on the diffserc or tos
Date: Tue, 18 Sep 2007 21:26:56 +0000 [thread overview]
Message-ID: <46F042A0.90102@ziu.info> (raw)
In-Reply-To: <ED9CC011977FDA4BAB13266D271118E6102B8A449F@BTSLMAIL.bhartitelesoft.com>
> Hi Michal,
>
> Can i user filter on the default qdisc attached on the eth0.If then how?
> (although i read somewhere that there is very little customization that
> we can do the default qdisc)?
Yes, default qdisc - pfifo_fast - is pretty limited, with 3 bands assigned
to specific tos values' combinations.
> If i used some classful qdisc than how would i restore my default
> setting?
Just delete the new qdisc you created, you will go back to pfifo_fast.
> Do we have better way achieving the same?
Well, HFSC or HTB would be a good choice, with SFQ or ESFQ attached to the
leafs (if i.e. using classes per groups of users).
> Can you suggest me some useful tutorials?
In no particular order (and not necessarily related to your questions):
1) Information about extended tc actions (mirred, ipt, ...) :
iproute2 tarball -> doc/actions
remark: currently it seems, that if you use more than 1 ipt
action in a filter rules, tc will segfault
Also look for info in Russel's docs
2) Excellent Russel's set of docs
http://ace-host.stuart.id.au/russell/files/tc/doc/
remark: contrary to other sources of info (i.e. lartc howto), the u32 docs
here are superbly accurate and (almost) complete.
minor missing info in u32:
indev purpose (?)
mark match (this one is simple, i.e. tc .... u32 match mark 1 flowid X:Y -
- note that flowid/classid must be last here, or tc will complain).
dscp can be used instead of tos
3) LARTC howto
http://lartc.org/#download
Pretty old, plenty of info, also plenty of missing info, and some
(like u32) leaving a LOT of important details (almost plain wrong).
4) iproute+tc notes
http://snafu.freedom.org/linux2.2/iproute-notes.html
Also can be found in iproute tarball. Missing info remarks as in 3)
5) Traffic control howto
http://tldp.org/HOWTO/Traffic-Control-HOWTO/index.html
6) Linux policy routing
http://www.policyrouting.org/PolicyRoutingBook/ONLINE/TOC.html
7) ip command reference
http://linux-ip.net/gl/ip-cref/
8) some elementary classification info (BASIC)
http://marc.info/?l=lartc&m\x117569441229800&w=2
9) some discussion with plenty of good info related to HFSC
http://marc.info/?t\x107799591400001&r=1&w=2
10) other HFSC documentation info
http://linux-ip.net/articles/hfsc.en/
http://www.cs.cmu.edu/~istoica/hfsc-tr.ps.gz (good, but detailed and long)
http://www.sonycsl.co.jp/~kjc/software/TIPS.txt (note that *BSD's HFSC
implementation, is a bit different (no concave curves, 80% limit on
realtime, ...). Good simple overview, but be careful.
11) marc.info, google, ...
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-09-18 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 10:28 [LARTC] using tc to drop packets based on the diffserc or tos value Raghuvendra Kumar
2007-09-16 20:36 ` [LARTC] using tc to drop packets based on the diffserc or tos Michal Soltys
2007-09-17 4:32 ` Raghuvendra Kumar
2007-09-17 6:48 ` Raghuvendra Kumar
2007-09-18 21:26 ` Michal Soltys [this message]
2007-09-19 4:23 ` Raghuvendra Kumar
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=46F042A0.90102@ziu.info \
--to=nozo@ziu.info \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.