matthias
/
iproute2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc/tc-filters.tex: Drop overly subjective paragraphs 

Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Signed-off-by: Phil Sutter <phil@nwl.cc>
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
This commit is contained in:
Phil Sutter 2016-03-22 15:48:32 +01:00 committed by Stephen Hemminger
parent 3c48c714a3
commit edf35b8824
1 changed files with 4 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/tc-filters.tex
View File

@ -18,10 +18,6 @@
\date{January 2016} \date{January 2016}
\maketitle \maketitle
TC, the Traffic Control utility, has been there for a very long time - forever
in my humble perception. It is still (and has ever been if I'm not mistaken) the
only tool to configure QoS in Linux.
Standard practice when transmitting packets over a medium which may block (due Standard practice when transmitting packets over a medium which may block (due
to congestion, e.g.) is to use a queue which temporarily holds these packets. In to congestion, e.g.) is to use a queue which temporarily holds these packets. In
Linux, this queueing approach is where QoS happens: A Queueing Discipline Linux, this queueing approach is where QoS happens: A Queueing Discipline
@ -496,21 +492,10 @@ kernel itself doesn't.
\section*{Conclusion} \section*{Conclusion}
My personal impression is that although the \cmd{tc} utility is an absolute Once the steep learning curve has been mastered, the conglomerate of (classful)
necessity for anyone aiming at doing QoS in Linux professionally, there are way qdiscs, filters and actions provides a highly sophisticated and flexible
too many loose ends and trip wires present in it's environment. Contributing to infrastructure to perform QoS, which plays nicely along with routing and
this is the fact, that much of the non-essential functionality is redundantly firewalling setups.
available in netfilter. Another problem which adds weight to the first one is a
general lack of documentation. Of course, there are many HOWTOs and guides in
the internet, but since it's often not clear how up to date these are, I prefer
the usual resources such as man or info pages. Surely nothing one couldn't fix
in hindsight, but quality certainly suffers if the original author of the code
does not or can not contribute to that.
All that being said, once the steep learning curve has been mastered, the
conglomerate of (classful) qdiscs, filters and actions provides a highly
sophisticated and flexible infrastructure to perform QoS, which plays nicely
along with routing and firewalling setups.
\section*{Further Reading} \section*{Further Reading}