send_io_resp_imm(9)
π¦ send_io_resp_imm(9) π¦
okay so bestie, this page is from the Kernel API Manual, and it's literally about send_io_resp_imm β yes, the whole title said send_io_resp_imm(9), and we're keeping that energy π
β¨ NAME β¨
send_io_resp_imm β respond to client with empty IMM on failed READ/WRITE requests or on successful WRITE request. no cap, that's the whole gig π«Ά
π SYNOPSIS π
int send_io_resp_imm (struct rtrs_srv_con *con , struct rtrs_srv_op *id
, int errno );
π ARGUMENTS π
conβ the connection that sends the result back to the client πidβ the id associated with the IO πerrnoβ the error number of the IO π¨
πΈ DESCRIPTION πΈ
It returns 0 on success, and errno otherwise. that's it, that's the function β¨
π₯ SEE ALSO π₯
Kernel file: ./drivers/infiniband/ulp/rtrs/rtrs-srv.c
rtrs_srv_resp_rdma(9)rtrs_srv_set_sess_priv(9)rtrs_srv_get_path_name(9)rtrs_srv_get_queue_depth(9)rtrs_srv_open(9)rtrs_srv_close(9)
go read those too, iykyk π
xoxo, from ./drivers/infiniband/ulp/rtrs, October 2026 β page send_io_resp_imm(9) π
β¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms