mpi3mr_get_num_trigger(9)
π« mpi3mr_get_num_trigger β Kernel API Manual edition, bestie π«
okay so this is a page straight out of the Kernel API Manual, and it's about mpi3mr_get_num_trigger(9) β a lil function that goes and counts your HDB triggers for you. yes, that kind of counting. slay. β¨
πΈ NAME πΈ
mpi3mr_get_num_trigger β gets number of HDB triggers</p> π
π¦ SYNOPSIS π¦
int mpi3mr_get_num_trigger (struct mpi3mr_ioc *mrioc , u8 *num_triggers
, u8 page_action );
that's the whole signature, no cap. three args, one int coming back at you. π
π ARGUMENTS π
mriocβ your adapter instance reference, i.e. the main character π of this whole operation.num_triggersβ literally just the number of triggers, that's the whole vibe π«Άpage_actionβ the page action. yes it matters, no we're not elaborating further on this page π
π DESCRIPTION π
so what does it actually do? it reads the number of triggers by reading driver page 2. that's it. that's the function. iconic, honestly β short, sweet, and to the point. π¦
β RETURN β
0on success π- proper error codes on failure π
π SEE ALSO π
okay this is the part where the manpage just goes off β like, the whole friend group showed up. every single one of these is real and you should go say hi:
- Kernel file
./drivers/scsi/mpi3mr/mpi3mr_app.cβ that's where the source lives, bestie, go read it π mpi3mr_alloc_trace_buffer(9)mpi3mr_alloc_diag_bufs(9)mpi3mr_issue_diag_buf_post(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_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)
like I said. the whole squad. ππ₯
and that's the page!! this masterpiece comes to you from ./drivers/scsi/mpi3mr and it's dated October 2026, titled mpi3mr_get_num_trigger(9) β so like, screenshot it, cite it, love it. 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