api: fix mp-safe mark for some messages and add more 25/38525/2
authorVladislav Grishenko <themiron@yandex-team.ru>
Sat, 18 Mar 2023 21:57:01 +0000 (02:57 +0500)
committerOle Tr�an <otroan@employees.org>
Wed, 6 Sep 2023 08:34:33 +0000 (08:34 +0000)
commite7c57c45aa981cee0b3376d63125c80c5c79e104
tree9d5e3f15ecda2af85f780fa7dfbbb2f76c283a23
parentdb8c2850812b210efde447b29bcd93a695ed4ed8
api: fix mp-safe mark for some messages and add more

Several api messages were not mp-safe although marked as such
because non-zero base id was not taken into account, and therefore
some other (from zero base id) were falsely mp-safe instead.

Keep messages as mp-safe, as they falsely were before:
    10   get_first_msg_id                              0       1
    12   api_versions                                  0       1

Messages that are no longer mp-safe as they weren't marked:
    15   sockclnt_create                               0       1
    33   proxy_arp_intfc_dump                          0       1

Fix messages to be really mp-safe:
    809  bridge_domain_dump                            0       1
    920  ip_route_add_del                              0       1
    921  ip_route_add_del_v2                           0       1
    1362 get_node_graph                                0       1
    1671 create_vhost_user_if                          0       1
    1675 create_vhost_user_if_v2                       0       1

Additionally mark messages as mp-safe, seems they need no barrier:
    1360 show_threads                                  0       1
    1370 show_version                                  0       1
    1372 show_vpe_system_time                          0       1

Type: fix
Change-Id: Ie6c1e3aa89f26bf51bfbcb7e7c4d9fee885487b7
Signed-off-by: Vladislav Grishenko <themiron@yandex-team.ru>
src/plugins/vhost/vhost_user_api.c
src/vlibmemory/memclnt_api.c
src/vlibmemory/vlib_api.c
src/vnet/ip/ip_api.c
src/vnet/l2/l2_api.c
src/vpp/api/api.c