Commit 7b229c3c authored by Adam Wujek's avatar Adam Wujek 💬

userspace/wrsw_rtud: change log level of creating/removing rtu entries

Since by default we use info level for messaging, on a busy, dynamic network
creating and removing rtu entries can produce a lot of syslog messages.
Signed-off-by: Adam Wujek's avatarAdam Wujek <adam.wujek@cern.ch>
parent bc4f2042
...@@ -325,7 +325,7 @@ int rtu_fd_create_entry(uint8_t mac[ETH_ALEN], uint16_t vid, uint32_t port_mask, ...@@ -325,7 +325,7 @@ int rtu_fd_create_entry(uint8_t mac[ETH_ALEN], uint16_t vid, uint32_t port_mask,
ent = &rtu_htab[eaddr.hash][eaddr.bucket]; ent = &rtu_htab[eaddr.hash][eaddr.bucket];
ent->addr = eaddr; ent->addr = eaddr;
pr_info( pr_debug(
"Created new entry for MAC %s : hash %03x:%d.\n", "Created new entry for MAC %s : hash %03x:%d.\n",
mac_to_string(mac), eaddr.hash, eaddr.bucket); mac_to_string(mac), eaddr.hash, eaddr.bucket);
...@@ -580,7 +580,7 @@ int rtu_fd_remove_entry(uint8_t *mac, uint32_t port_mask, int type) ...@@ -580,7 +580,7 @@ int rtu_fd_remove_entry(uint8_t *mac, uint32_t port_mask, int type)
/* entry is _only_ for this port */ /* entry is _only_ for this port */
hw_request(HW_REMOVE_REQ, ent->addr, hw_request(HW_REMOVE_REQ, ent->addr,
ent); ent);
pr_info("Cleaning %s entry for mask=0x%x MAC: " pr_debug("Cleaning %s entry for mask=0x%x MAC: "
"%s type %s\n", "%s type %s\n",
is_unicast(port_mask) ? is_unicast(port_mask) ?
"unicast" : "multicast", "unicast" : "multicast",
...@@ -674,7 +674,7 @@ static void delete_htab_entry(struct rtu_addr addr) ...@@ -674,7 +674,7 @@ static void delete_htab_entry(struct rtu_addr addr)
{ {
int i, n_buckets = htab_count_buckets(addr); int i, n_buckets = htab_count_buckets(addr);
pr_info("Deleted entry for MAC %s : hash %03x:%d.\n", pr_debug("Deleted entry for MAC %s : hash %03x:%d.\n",
mac_to_string(rtu_htab[addr.hash][addr.bucket].mac), addr.hash, mac_to_string(rtu_htab[addr.hash][addr.bucket].mac), addr.hash,
addr.bucket); addr.bucket);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment