nmlx5_core_en_uplink.c: within vmkernel.log on esxi - repeat messages - what do they mean?

Hi everybody,

maybe someone can help me to read some special vmkernel log messages

I try to iron out some problem on an iscsi network an the logs bring up those messsages every view minutes

2019-09-25T13:26:22.752Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineSupportedConfigGet - (nmlx5_core_en_uplink.c:1541) called

2019-09-25T13:26:22.752Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineSupportedConfigGet - (nmlx5_core_en_uplink.c:1577) RSS Engine queue [9] supports 3 max. sec. queues

2019-09-25T13:26:22.752Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineSupportedConfigGet - (nmlx5_core_en_uplink.c:1591) done, status: Success

2019-09-25T13:26:22.752Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineCurrentConfigGet - (nmlx5_core_en_uplink.c:1631) called

2019-09-25T13:26:22.752Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineCurrentConfigGet - (nmlx5_core_en_uplink.c:1665) RSS Engine queue [9] currently has 1 HW queues

2019-09-25T13:26:22.752Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineCurrentConfigGet - (nmlx5_core_en_uplink.c:1678) done, status: Success

2019-09-25T13:26:22.752Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineConfigSet - (nmlx5_core_en_uplink.c:1721) called

2019-09-25T13:26:22.752Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_RssEngineInitSecQueues - (nmlx5_core_en_uplink.c:1385) called

2019-09-25T13:26:22.752Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_RssEngineInitSecQueues - (nmlx5_core_en_uplink.c:1396) Requested to init. 3 secondary queues for queue [9]

2019-09-25T13:26:22.755Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_RssEngineInitSecQueues - (nmlx5_core_en_uplink.c:1439) done, status: Success

2019-09-25T13:26:22.755Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineConfigSet - (nmlx5_core_en_uplink.c:1762) done, status = Success

2019-09-25T13:26:22.755Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineConfigSet - (nmlx5_core_en_uplink.c:1721) called

2019-09-25T13:26:22.755Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineConfigSet - (nmlx5_core_en_uplink.c:1747) Hash key set of size 40 requested for queue [9]

2019-09-25T13:26:22.755Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineConfigSet - (nmlx5_core_en_uplink.c:1762) done, status = Not supported

2019-09-25T13:26:22.755Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineIndTableSet - (nmlx5_core_en_uplink.c:1802) called for RSS engine queue [9]

2019-09-25T13:26:22.755Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssIndirTableStore - (nmlx5_core_en_uplink.c:1138) Indirection table updated for queue [9]

2019-09-25T13:26:22.755Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssIndirTableStore - (nmlx5_core_en_uplink.c:1153) done, status = Success

2019-09-25T13:26:22.757Z cpu44:2097388)<NMLX_INF> nmlx5_core: vmnic0: nmlx5_en_QueueRssEngineIndTableSet - (nmlx5_core_en_uplink.c:1806) done, status:

I see a case opened with Mellanox Support assigned to our EMEA support team.

[00666104] ConnectX-5 and esxi 6.7 - regular vmkernel.log entries

I am also seeing similar messages in vmkernel.log on ESXi 6.7U3. It also has an iSCSI target attached via software iSCSI adapter on ESXi.

Should I be worried about these messages? I am seeing perf issues on my iSCSI datastore.