lacp: mark is_mp_safe for show and dump binary API
show and dump binary APIs for lacp neighbors are running in the same thread as the create and delete interface. There is no need for barrier lock. Type: fix Signed-off-by: Steven Luong <sluong@cisco.com> Change-Id: Id584bd7408210fcc23b464ef2084f11f88bca58b
This commit is contained in:
committed by
Damjan Marion
parent
29ab3446c6
commit
cda35b38d7
@@ -315,6 +315,7 @@ VLIB_CLI_COMMAND (show_lacp_command, static) = {
|
||||
.path = "show lacp",
|
||||
.short_help = "show lacp [<interface>] [details]",
|
||||
.function = show_lacp_fn,
|
||||
.is_mp_safe = 1,
|
||||
};
|
||||
/* *INDENT-ON* */
|
||||
|
||||
|
||||
@@ -190,6 +190,10 @@ lacp_plugin_api_hookup (vlib_main_t * vm)
|
||||
foreach_lacp_plugin_api_msg;
|
||||
#undef _
|
||||
|
||||
/* Mark these APIs as mp safe */
|
||||
am->is_mp_safe[VL_API_SW_INTERFACE_LACP_DUMP] = 1;
|
||||
am->is_mp_safe[VL_API_SW_INTERFACE_LACP_DETAILS] = 1;
|
||||
|
||||
/*
|
||||
* Set up the (msg_name, crc, message-id) table
|
||||
*/
|
||||
|
||||
Reference in New Issue
Block a user