diff options
| author | Christian Poessinger <christian@poessinger.com> | 2020-09-16 22:32:04 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-09-16 22:32:04 +0200 |
| commit | 1a7b4c65fa9507a37d564908407f3e6da2903a01 (patch) | |
| tree | 5aacc11870f9b98cd2d91b3e92745dc5cd045f00 | |
| parent | 3f3fa04dbd3c5a39323e453b90bc2e1f8d08ddb4 (diff) | |
| parent | 998339f92db664ec71fea189ba38bd38e6a6c4a6 (diff) | |
| download | vyos-documentation-1a7b4c65fa9507a37d564908407f3e6da2903a01.tar.gz vyos-documentation-1a7b4c65fa9507a37d564908407f3e6da2903a01.zip | |
Merge pull request #331 from currite/backport-qos-hint
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 --------- |