|
 |
049c96 |
From 099c84e5b772f0fc5ec2f0176e74330a4e4ec0cb Mon Sep 17 00:00:00 2001
|
|
|
049c96 |
From: Phil Sutter <psutter@redhat.com>
|
|
|
049c96 |
Date: Wed, 30 Mar 2016 16:51:38 +0200
|
|
|
049c96 |
Subject: [PATCH] doc/tc-filters.tex: Drop overly subjective paragraphs
|
|
|
049c96 |
|
|
|
049c96 |
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1275426
|
|
|
049c96 |
Upstream Status: iproute2.git commit edf35b88248f6
|
|
|
049c96 |
|
|
|
049c96 |
commit edf35b88248f667c0b4f1502ccd35ce423d12451
|
|
|
049c96 |
Author: Phil Sutter <phil@nwl.cc>
|
|
|
049c96 |
Date: Tue Mar 22 15:48:32 2016 +0100
|
|
|
049c96 |
|
|
|
049c96 |
doc/tc-filters.tex: Drop overly subjective paragraphs
|
|
|
049c96 |
|
|
|
049c96 |
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
|
|
|
049c96 |
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
|
049c96 |
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
|
|
|
049c96 |
---
|
|
|
049c96 |
doc/tc-filters.tex | 23 ++++-------------------
|
|
|
049c96 |
1 file changed, 4 insertions(+), 19 deletions(-)
|
|
|
049c96 |
|
|
|
049c96 |
diff --git a/doc/tc-filters.tex b/doc/tc-filters.tex
|
|
|
049c96 |
index 59127d6..54cc0c9 100644
|
|
|
049c96 |
--- a/doc/tc-filters.tex
|
|
|
049c96 |
+++ b/doc/tc-filters.tex
|
|
|
049c96 |
@@ -18,10 +18,6 @@
|
|
|
049c96 |
\date{January 2016}
|
|
|
049c96 |
\maketitle
|
|
|
049c96 |
|
|
|
049c96 |
-TC, the Traffic Control utility, has been there for a very long time - forever
|
|
|
049c96 |
-in my humble perception. It is still (and has ever been if I'm not mistaken) the
|
|
|
049c96 |
-only tool to configure QoS in Linux.
|
|
|
049c96 |
-
|
|
|
049c96 |
Standard practice when transmitting packets over a medium which may block (due
|
|
|
049c96 |
to congestion, e.g.) is to use a queue which temporarily holds these packets. In
|
|
|
049c96 |
Linux, this queueing approach is where QoS happens: A Queueing Discipline
|
|
|
049c96 |
@@ -496,21 +492,10 @@ kernel itself doesn't.
|
|
|
049c96 |
|
|
|
049c96 |
\section*{Conclusion}
|
|
|
049c96 |
|
|
|
049c96 |
-My personal impression is that although the \cmd{tc} utility is an absolute
|
|
|
049c96 |
-necessity for anyone aiming at doing QoS in Linux professionally, there are way
|
|
|
049c96 |
-too many loose ends and trip wires present in it's environment. Contributing to
|
|
|
049c96 |
-this is the fact, that much of the non-essential functionality is redundantly
|
|
|
049c96 |
-available in netfilter. Another problem which adds weight to the first one is a
|
|
|
049c96 |
-general lack of documentation. Of course, there are many HOWTOs and guides in
|
|
|
049c96 |
-the internet, but since it's often not clear how up to date these are, I prefer
|
|
|
049c96 |
-the usual resources such as man or info pages. Surely nothing one couldn't fix
|
|
|
049c96 |
-in hindsight, but quality certainly suffers if the original author of the code
|
|
|
049c96 |
-does not or can not contribute to that.
|
|
|
049c96 |
-
|
|
|
049c96 |
-All that being said, once the steep learning curve has been mastered, the
|
|
|
049c96 |
-conglomerate of (classful) qdiscs, filters and actions provides a highly
|
|
|
049c96 |
-sophisticated and flexible infrastructure to perform QoS, which plays nicely
|
|
|
049c96 |
-along with routing and firewalling setups.
|
|
|
049c96 |
+Once the steep learning curve has been mastered, the conglomerate of (classful)
|
|
|
049c96 |
+qdiscs, filters and actions provides a highly sophisticated and flexible
|
|
|
049c96 |
+infrastructure to perform QoS, which plays nicely along with routing and
|
|
|
049c96 |
+firewalling setups.
|
|
|
049c96 |
|
|
|
049c96 |
|
|
|
049c96 |
\section*{Further Reading}
|
|
|
049c96 |
--
|
|
|
049c96 |
1.8.3.1
|
|
|
049c96 |
|