mpi3mr_get_change_count(9)
π mpi3mr_get_change_count π
okay so this is a Kernel API Manual page, bestie β we're deep in kernel-land today, and honestly? iconic of you to be here.
β¨ NAME β¨
mpi3mr_get_change_count β get that topology change count, fr fr π¦
πΈ SYNOPSIS πΈ
long mpi3mr_get_change_count (struct mpi3mr_ioc *mrioc , struct bsg_job
*job );
π ARGUMENTS π
mriocβ the adapter instance reference, aka your controller's whole vibe πjobβ the BSG job reference, the little errand this call is running for π§
π DESCRIPTION π
So here's what's happening, no cap: the driver keeps a topology change count, it hands that bad boy over in events, and then it gets cached right there in the driver. This function's whole job is copying that cached count into the user-provided buffer β you know, the one for that specific controller. Not a different controller. That one. π
it's giving "middleman but make it useful" β¨
π₯ RETURN π₯
0 on success, and proper error codes if it doesn't slay ππ
π SEE ALSO π
a whole squad, honestly β look at this lineup π
- Kernel file
./drivers/scsi/mpi3mr/mpi3mr_app.c
and then the friends:
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_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_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)
π reminder bestie: that list is literal β every single one of those (9) pages is a real reference, so don't go trimming it for the aesthetic. iykyk.
okay that's the whole page, you ate that π«Ά this cutie lives in ./drivers/scsi/mpi3mr and it's dated October 2026 β yes, the future, main character energy only βππ
π¦ 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