mpi3mr_post_diag_bufs(9)
π mpi3mr_post_diag_bufs β post diag buffers to the controller π
okay bestie, welcome to the mpi3mr_post_diag_bufs(9) page, straight out of the Kernel API Manual β¨ grab a lil snack, this one's short and sweet.
β¨ NAME β¨
mpi3mr_post_diag_bufs β literally just post diag buffers to the controller π that's it, that's the whole vibe.
β¨ SYNOPSIS β¨
int mpi3mr_post_diag_bufs (struct mpi3mr_ioc *mrioc );
so you call it with one arg and it hands you back an int, periodt π
β¨ ARGUMENTS β¨
mriocβ the adapter instance reference π«Ά like, the whole controller's main character ID. you gotta hand it over so the function knows which adapter we're talking to.
β¨ DESCRIPTION β¨
okay so here's the tea β this function calls a helper function to post both the trace buffers and the firmware buffers to the controller. both of them. together. it's giving teamwork πβ¨
no cap, that's the entire description β it's a little wrapper-ish situation that just makes sure both buffer types get posted to the controller through its helper. simple, iconic, does its job π
β¨ RETURN β¨
None π«Ά the manpage says none, so we're saying none. don't come for me, i just report the facts bestie π
β¨ SEE ALSO β¨
the friend group π―ββοΈπ the kernel file lives at ./drivers/scsi/mpi3mr/mpi3mr_app.c β go say hi.
and here's the whole squad, no cap, all of them, in order:
mpi3mr_alloc_trace_buffer(9)mpi3mr_alloc_diag_bufs(9)mpi3mr_issue_diag_buf_post(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)
and that's the whole page bestie, you ate that π β¨
later, from ./drivers/scsi/mpi3mr β October 2026 era, and yes, this was mpi3mr_post_diag_bufs(9) the whole time π¦π see u in the next one, mwah π
π¦ 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