netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [iproute PATCH] man: ip-rule.8: Further clarify how to interpret priority value
@ 2017-04-24 15:35 Phil Sutter
  2017-04-24 18:44 ` Stephen Hemminger
  0 siblings, 1 reply; 2+ messages in thread
From: Phil Sutter @ 2017-04-24 15:35 UTC (permalink / raw)
  To: Stephen Hemminger; +Cc: netdev

Despite the past changes, users seemed to get confused by the seemingly
contradictory relation of priority value and actual rule priority.

Signed-off-by: Phil Sutter <phil@nwl.cc>
---
 man/man8/ip-rule.8 | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/man/man8/ip-rule.8 b/man/man8/ip-rule.8
index 7de80f3e6db9f..a5c479811927f 100644
--- a/man/man8/ip-rule.8
+++ b/man/man8/ip-rule.8
@@ -95,7 +95,10 @@ Each policy routing rule consists of a
 .B selector
 and an
 .B action predicate.
-The RPDB is scanned in order of decreasing priority. The selector
+The RPDB is scanned in order of decreasing priority (note that lower number
+means higher priority, see the description of
+.I PREFERENCE
+below). The selector
 of each rule is applied to {source address, destination address, incoming
 interface, tos, fwmark} and, if the selector matches the packet,
 the action is performed. The action predicate may return with success.
@@ -225,7 +228,8 @@ value to match.
 .BI priority " PREFERENCE"
 the priority of this rule.
 .I PREFERENCE
-is an unsigned integer value, higher number means lower priority.  Each rule
+is an unsigned integer value, higher number means lower priority, and rules get
+processed in order of increasing number. Each rule
 should have an explicitly set
 .I unique
 priority value.
-- 
2.11.0

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [iproute PATCH] man: ip-rule.8: Further clarify how to interpret priority value
  2017-04-24 15:35 [iproute PATCH] man: ip-rule.8: Further clarify how to interpret priority value Phil Sutter
@ 2017-04-24 18:44 ` Stephen Hemminger
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2017-04-24 18:44 UTC (permalink / raw)
  To: Phil Sutter; +Cc: netdev

On Mon, 24 Apr 2017 17:35:37 +0200
Phil Sutter <phil@nwl.cc> wrote:

> Despite the past changes, users seemed to get confused by the seemingly
> contradictory relation of priority value and actual rule priority.
> 
> Signed-off-by: Phil Sutter <phil@nwl.cc>

Makes sense. Applied.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-04-24 18:44 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-04-24 15:35 [iproute PATCH] man: ip-rule.8: Further clarify how to interpret priority value Phil Sutter
2017-04-24 18:44 ` Stephen Hemminger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).