mpi3mr_issue_diag_buf_post(9)
π mpi3mr_issue_diag_buf_post(9) π
okay so bestie, welcome to the Kernel API Manual entry for mpi3mr_issue_diag_buf_post β yes the name is a mouthful, no I will not be shortening it, we respect the full government name here π«Ά
β¨ NAME β¨
mpi3mr_issue_diag_buf_post β literally just sends the diag buffer post req. that's the whole job. she's a one-task queen π
πΈ SYNOPSIS πΈ
int mpi3mr_issue_diag_buf_post (struct mpi3mr_ioc *mrioc , struct
diag_buffer_desc *diag_buffer );
π ARGUMENTS π
mriocβ your adapter instance reference. the main character of the whole driver, honestly πdiag_bufferβ the diagnostic buffer descriptor. yes she's a struct, yes she's coming with us π¦
β DESCRIPTION β
so here's the vibe: this function issues the diagnostic buffer post MPI request through the admin queue, and then it just waits β politely, patiently β for that request to complete. or for it to time out. whichever hits first π
no cap, that's it. send the request, wait for the completion, respect the timeout. iconic behaviour.
π₯ RETURN π₯
0on success β slay π- non-zero on failures β not slay, but at least you know π
π SEE ALSO π
kay so this is the part where I list literally everyone in the group chat, and I mean everyone β no skipping, we don't do that here π«Ά
- Kernel file
./drivers/scsi/mpi3mr/mpi3mr_app.c mpi3mr_alloc_trace_buffer(9)mpi3mr_alloc_diag_bufs(9)mpi3mr_post_diag_bufs(9)mpi3mr_issue_diag_buf_release(9)mpi3mr_process_trigger(9)mpi3mr_global_trigger(9)mpi3mr_scsisense_trigger(9)mpi3mr_event_trigger(9)mpi3mr_reply_trigger(9)mpi3mr_get_num_trigger(9)mpi3mr_refresh_trigger(9)mpi3mr_release_diag_bufs(9)mpi3mr_set_trigger_data_in_hdb(9)mpi3mr_set_trigger_data_in_all_hdb(9)mpi3mr_hdbstatuschg_evt_th(9)mpi3mr_diag_buffer_for_type(9)mpi3mr_bsg_pel_abort(9)mpi3mr_bsg_verify_adapter(9)mpi3mr_bsg_refresh_hdb_triggers(9)mpi3mr_bsg_upload_hdb(9)mpi3mr_bsg_repost_hdb(9)mpi3mr_bsg_query_hdb(9)mpi3mr_enable_logdata(9)mpi3mr_get_logdata(9)mpi3mr_bsg_pel_enable(9)mpi3mr_get_all_tgt_info(9)mpi3mr_get_change_count(9)mpi3mr_bsg_adp_reset(9)mpi3mr_bsg_populate_adpinfo(9)mpi3mr_bsg_process_drv_cmds(9)mpi3mr_total_num_ioctl_sges(9)mpi3mr_bsg_build_sgl(9)mpi3mr_get_nvme_data_fmt(9)mpi3mr_build_nvme_sgl(9)mpi3mr_build_nvme_prp(9)mpi3mr_map_data_buffer_dma(9)mpi3mr_bsg_process_mpt_cmds(9)mpi3mr_app_save_logdata_th(9)mpi3mr_bsg_request(9)mpi3mr_bsg_exit(9)mpi3mr_bsg_node_release(9)mpi3mr_bsg_init(9)version_fw_show(9)fw_queue_depth_show(9)op_req_q_count_show(9)reply_queue_count_show(9)reply_qfull_count_show(9)logging_level_show(9)logging_level_store(9)adp_state_show(9)fwfault_count_show(9)sas_address_show(9)device_handle_show(9)persistent_id_show(9)sas_ncq_prio_supported_show(9)sas_ncq_prio_enable_show(9)
π§ quick vibe check: this page lives in ./drivers/scsi/mpi3mr and it's dated October 2026 β so yeah, this manual is from the future, we love a forward-thinking queen β
okay that's the whole page, ily, go read your kernel source bestie ππ
π¦ 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