diff options
| author | Leon Romanovsky <[email protected]> | 2018-06-24 11:23:46 +0300 |
|---|---|---|
| committer | Leon Romanovsky <[email protected]> | 2018-06-27 08:43:55 +0300 |
| commit | b30408d7a38356e4d6b4f913686b25401fae386c (patch) | |
| tree | e0aa867eb5eca0b7725ae3dbad6172099929be5a /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 0af5107cd0640ee3424e337b492e4b11b450ce28 (diff) | |
net/mlx5: Rate limit errors in command interface
Any error status returned by FW will trigger a print similar to the
following error message in the dmesg.
[ 55.884355] mlx5_core 0000:00:04.0: mlx5_cmd_check:712:(pid 555):
ALLOC_UAR(0x802) op_mod(0x0) failed, status limits exceeded(0x8),
syndrome (0x0)
Those prints are extremely valuable to diagnose issues with running system
and it is important to keep them. However, not-so-careful user can trigger
endless number of such prints by depleting HW resources and will spam
dmesg.
Rate limiting of such messages solves this issue.
Signed-off-by: Leon Romanovsky <[email protected]>
Signed-off-by: Jason Gunthorpe <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions