diff options
author | Amir Vadai <amirva@mellanox.com> | 2016-05-13 12:55:41 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-05-16 13:43:51 -0400 |
commit | 43a335e055bb7ebdc8a68ce7362ef26ef5bda92b (patch) | |
tree | 0441f14934b5e341f12df45bc86bbca9c3dc3d03 /drivers/net/ethernet/mellanox/mlx5/core/en_main.c | |
parent | bd5251dbf156b6bc0661a9409d46e47160df61dd (diff) |
net/mlx5_core: Flow counters infrastructure
If a counter has the aging flag set when created, it is added to a list
of counters that will be queried periodically from a workqueue. query
result and last use timestamp are cached.
add/del counter must be very efficient since thousands of such
operations might be issued in a second.
There is only a single reference to counters without aging, therefore
no need for locks.
But, counters with aging enabled are stored in a list. In order to make
code as lockless as possible, all the list manipulation and access to
hardware is done from a single context - the periodic counters query
thread.
The hardware supports multiple counters per FTE, however currently we
are using one counter for each FTE.
Signed-off-by: Amir Vadai <amirva@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/mellanox/mlx5/core/en_main.c')
0 files changed, 0 insertions, 0 deletions