diff options
author | currite <sll@disroot.org> | 2020-09-15 10:28:07 +0200 |
---|---|---|
committer | currite <sll@disroot.org> | 2020-09-15 10:28:07 +0200 |
commit | fc94b0cfd7682fc9eacc4fbe506cd55744759703 (patch) | |
tree | 0e6e584def153c4ef7354c74946aae8e67b8dc76 | |
parent | 910fa1ab3ac6a26959f0a2fb4915bf3c0791f720 (diff) | |
download | vyos-documentation-fc94b0cfd7682fc9eacc4fbe506cd55744759703.tar.gz vyos-documentation-fc94b0cfd7682fc9eacc4fbe506cd55744759703.zip |
qos: improve hint on choosing policy
-rw-r--r-- | docs/qos.rst | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/docs/qos.rst b/docs/qos.rst index a4e56665..3cd183cf 100644 --- a/docs/qos.rst +++ b/docs/qos.rst @@ -336,12 +336,11 @@ you will only be able to apply one policy per interface and direction Some policies can be combined, you will be able to embed_ a different policy that will be applied to a class of the main policy. -.. hint:: If you are looking for a policy for your outbound traffic but - you do not know what policy you need, you might consider FQ-CoDel_ as - your multipurpose nearly-no-configuration low-delay fair-queue - policy; if delay does not worry you and you want to manually allocate - bandwidth shares to specific traffic, then you should consider - Shaper_. +.. hint:: **If you are looking for a policy for your outbound traffic** + but you don't know which one you need and you don't want to go + through every possible policy shown here, **our bet is that highly + likely you are looking for a** Shaper_ **policy and you want to** + :ref:`set its queues <embed>` **as FQ-CoDel**. Drop Tail --------- |