Searched hist:"1 b2a4440858857f2f93bb2ec5bb3a60f4fcc25be" (Results 1 – 5 of 5) sorted by relevance
| /linux/net/ipv4/ |
| H A D | fib_notifier.c | diff 1b2a4440858857f2f93bb2ec5bb3a60f4fcc25be Thu Aug 03 13:28:14 CEST 2017 Ido Schimmel <idosch@mellanox.com> net: fib_rules: Implement notification logic in core
Unlike the routing tables, the FIB rules share a common core, so instead
of replicating the same logic for each address family we can simply dump
the rules and send notifications from the core itself.
To protect the integrity of the dump, a rules-specific sequence counter
is added for each address family and incremented whenever a rule is
added or deleted (under RTNL).
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | fib_rules.c | diff 1b2a4440858857f2f93bb2ec5bb3a60f4fcc25be Thu Aug 03 13:28:14 CEST 2017 Ido Schimmel <idosch@mellanox.com> net: fib_rules: Implement notification logic in core
Unlike the routing tables, the FIB rules share a common core, so instead
of replicating the same logic for each address family we can simply dump
the rules and send notifications from the core itself.
To protect the integrity of the dump, a rules-specific sequence counter
is added for each address family and incremented whenever a rule is
added or deleted (under RTNL).
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /linux/include/net/ |
| H A D | fib_rules.h | diff 1b2a4440858857f2f93bb2ec5bb3a60f4fcc25be Thu Aug 03 13:28:14 CEST 2017 Ido Schimmel <idosch@mellanox.com> net: fib_rules: Implement notification logic in core
Unlike the routing tables, the FIB rules share a common core, so instead
of replicating the same logic for each address family we can simply dump
the rules and send notifications from the core itself.
To protect the integrity of the dump, a rules-specific sequence counter
is added for each address family and incremented whenever a rule is
added or deleted (under RTNL).
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | ip_fib.h | diff 1b2a4440858857f2f93bb2ec5bb3a60f4fcc25be Thu Aug 03 13:28:14 CEST 2017 Ido Schimmel <idosch@mellanox.com> net: fib_rules: Implement notification logic in core
Unlike the routing tables, the FIB rules share a common core, so instead
of replicating the same logic for each address family we can simply dump
the rules and send notifications from the core itself.
To protect the integrity of the dump, a rules-specific sequence counter
is added for each address family and incremented whenever a rule is
added or deleted (under RTNL).
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /linux/net/core/ |
| H A D | fib_rules.c | diff 1b2a4440858857f2f93bb2ec5bb3a60f4fcc25be Thu Aug 03 13:28:14 CEST 2017 Ido Schimmel <idosch@mellanox.com> net: fib_rules: Implement notification logic in core
Unlike the routing tables, the FIB rules share a common core, so instead
of replicating the same logic for each address family we can simply dump
the rules and send notifications from the core itself.
To protect the integrity of the dump, a rules-specific sequence counter
is added for each address family and incremented whenever a rule is
added or deleted (under RTNL).
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|