RE: [PATCH v2] IB/mlx4: delete allocated id_map_entry while sending REJ

[Praveen Kannoju]

Oracle Confidential

Thank you very much, Leon.

-
Praveen.


Oracle Confidential
+AD4- -----Original Message-----
+AD4- From: Leon Romanovsky +ADw-leon+AEA-kernel.org+AD4-
+AD4- Sent: Monday, July 13, 2026 2:06 PM
+AD4- To: yishaih+AEA-nvidia.com+ADs- jgg+AEA-ziepe.ca+ADs- linux-rdma+AEA-vger.kernel.org+ADs- linux-
+AD4- kernel+AEA-vger.kernel.org+ADs- Praveen Kannoju +ADw-praveen.kannoju+AEA-oracle.com+AD4-
+AD4- Cc: Manjunath Patil +ADw-manjunath.b.patil+AEA-oracle.com+AD4AOw- Anand Khoje
+AD4- +ADw-anand.a.khoje+AEA-oracle.com+AD4-
+AD4- Subject: Re: +AFs-PATCH v2+AF0- IB/mlx4: delete allocated id+AF8-map+AF8-entry while sending
+AD4- REJ
+AD4-
+AD4-
+AD4- On Mon, 15 Jun 2026 17:17:59 +-0000, Praveen Kumar Kannoju wrote:
+AD4- +AD4- The mlx4 CM paravirtualization layer rewrites a VF's local
+AD4- +AD4- communication ID to a PF-visible ID when CM MADs are sent from the VF.
+AD4- +AD4- For messages that start or advance a connection from the VF side, such
+AD4- +AD4- as REQ, REP, MRA and SIDR+AF8-REQ, mlx4+AF8-ib+AF8-multiplex+AF8-cm+AF8-handler()
+AD4- +AD4- allocates an id+AF8-map+AF8-entry when no existing mapping is found.
+AD4- +AD4-
+AD4- +AD4- A REJ is different because it is a terminal response to an already
+AD4- +AD4- known exchange. It should either find an existing id+AF8-map+AF8-entry,
+AD4- +AD4- rewrite the local communication ID, and schedule that entry for
+AD4- +AD4- deletion, or it should pass through unchanged when no mapping exists.
+AD4- +AD4-
+AD4- +AD4- +AFs-...+AF0-
+AD4-
+AD4- Applied, thanks+ACE-
+AD4-
+AD4- +AFs-1/1+AF0- IB/mlx4: delete allocated id+AF8-map+AF8-entry while sending REJ
+AD4-       https://git.kernel.org/rdma/rdma/c/9539e619660471
+AD4-
+AD4- Best regards,
+AD4- --
+AD4- Leon Romanovsky +ADw-leon+AEA-kernel.org+AD4-