diff options
author | Marius Strobl <marius@FreeBSD.org> | 2024-02-05 19:36:13 +0000 |
---|---|---|
committer | Marius Strobl <marius@FreeBSD.org> | 2024-02-05 22:44:38 +0000 |
commit | ed81a15517b8a8f587fd7282c3690513bb798242 (patch) | |
tree | d9a69d18c37e37b6f2b5fee96235386b834336a8 | |
parent | 069c6ac2c698db68983efd17198e9c202c976d25 (diff) | |
download | src-ed81a15517b8a8f587fd7282c3690513bb798242.tar.gz src-ed81a15517b8a8f587fd7282c3690513bb798242.zip |
fib_algo(4): Lower level of algorithm switching messages to LOG_INFO
Otherwise, with the default flm_debug_level of LOG_NOTICE, it's rather
easy to trigger debug messages such as:
[fib_algo] inet.0 (bsearch4#18) rebuild_fd_flm: switching algo to
radix4_lockless
Also, the "severity" of these events generally only justifies LOG_INFO
and not LOG_NOTICE.
Reviewed by: melifaro
-rw-r--r-- | sys/net/route/fib_algo.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/net/route/fib_algo.c b/sys/net/route/fib_algo.c index 1e37acf620a9..25370f18934f 100644 --- a/sys/net/route/fib_algo.c +++ b/sys/net/route/fib_algo.c @@ -1382,7 +1382,7 @@ rebuild_fd_flm(struct fib_data *fd, struct fib_lookup_module *flm_new) if (flm_new == fd->fd_flm) fd_tmp = fd; else - FD_PRINTF(LOG_NOTICE, fd, "switching algo to %s", flm_new->flm_name); + FD_PRINTF(LOG_INFO, fd, "switching algo to %s", flm_new->flm_name); result = setup_fd_instance(flm_new, fd->fd_rh, fd_tmp, &fd_new, true); if (result != FLM_SUCCESS) { |