diff options
| author | Donald Sharp <sharpd@nvidia.com> | 2021-02-03 15:13:59 +0100 |
|---|---|---|
| committer | Donald Sharp <sharpd@nvidia.com> | 2022-01-20 17:56:27 +0100 |
| commit | ab01a00176db60080047731ab548136e773b6c51 (patch) | |
| tree | dbfb8df8a6273dbbf259ec19f89e2484508f1921 /lib/lib_errors.c | |
| parent | Merge pull request #10360 from opensourcerouting/clippy-rel-endian (diff) | |
| download | frr-ab01a00176db60080047731ab548136e773b6c51.tar.xz frr-ab01a00176db60080047731ab548136e773b6c51.zip | |
lib: Figure out if we are being starved for cpu
If a thread timer should have popped CPU_CONSUMED_CHECK
seconds in the past, and we are only handling it now. Consider
the thread starved and notice it.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'lib/lib_errors.c')
| -rw-r--r-- | lib/lib_errors.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/lib/lib_errors.c b/lib/lib_errors.c index a139b9a14..acc9a05c3 100644 --- a/lib/lib_errors.c +++ b/lib/lib_errors.c @@ -57,6 +57,12 @@ static struct log_ref ferr_lib_warn[] = { .suggestion = "Gather log data and open an Issue", }, { + .code = EC_LIB_STARVE_THREAD, + .title = "The Event subsystem has detected a thread starvation issue", + .description = "The event subsystem has detected a thread starvation issue. This typically indicates that the system FRR is running on is heavily loaded and this load might be impacting FRR's ability to handle events in a timely fashion", + .suggestion = "Gather log data and open an Issue", + }, + { .code = EC_LIB_NO_THREAD, .title = "The Event subsystem has detected an internal FD problem", .description = "The Event subsystem has detected a file descriptor read/write event without an associated handling function. This is a bug, please collect log data and open an issue.", |