diff options
| author | Håkon Bugge <haakon.bugge@oracle.com> | 2025-10-21 15:27:33 +0200 |
|---|---|---|
| committer | Leon Romanovsky <leon@kernel.org> | 2025-10-27 07:36:39 -0400 |
| commit | 58aca1f3de059c19262550fab6dba150f9d5f989 (patch) | |
| tree | f5f4032510ad3aef7ffb26f8987867a9aa989cdf /tools/perf/scripts/python/stackcollapse.py | |
| parent | be180c847a6db6646d7bb4740a1d73f6f67d1030 (diff) | |
RDMA/cm: Base cm_id destruction timeout on CMA values
When a GSI MAD packet is sent on the QP, it will potentially be
retried CMA_MAX_CM_RETRIES times with a timeout value of:
4.096usec * 2 ^ CMA_CM_RESPONSE_TIMEOUT
The above equates to ~64 seconds using the default CMA values.
The cm_id_priv's refcount will be incremented for this period.
Therefore, the timeout value waiting for a cm_id destruction must be
based on the effective timeout of MAD packets. To provide additional
leeway, we add 25% to this timeout and use that instead of the
constant 10 seconds timeout, which may result in false negatives.
Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
Link: https://patch.msgid.link/20251021132738.4179604-1-haakon.bugge@oracle.com
Signed-off-by: Leon Romanovsky <leon@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions