mpi3mr_get_all_tgt_info(9)
β¨ mpi3mr_get_all_tgt_info(9) β¨
okay so this is a page from the Kernel API Manual and bestie, it's literally about mpi3mr_get_all_tgt_info β the function that tells userspace everything about the targets a controller is managing. let's get into it π
πΈ NAME πΈ
mpi3mr_get_all_tgt_info β Get all target information π―
π¦ SYNOPSIS π¦
long mpi3mr_get_all_tgt_info (struct mpi3mr_ioc *mrioc , struct bsg_job
*job );
π ARGUMENTS π
mriocβ the adapter instance reference, aka your controller's whole vibe and identity π«Άjobβ the BSG job reference, aka the request that's asking for the tea β
π DESCRIPTION π
so what does it actually do? this function copies the driver-managed target devices' device handle, persistent ID, bus ID and target ID into the user-provided buffer β and it does that for the specific controller you point it at. no cap, that's the whole errand π§
and like, that's not even all of it β this function also hands back the number of devices managed by the driver for that specific controller. it's giving "here's everyone plus a headcount" main character energy π
β RETURN β
0 on success, and proper error codes on failure. that's it, that's the deal π
π₯ SEE ALSO π₯
Kernel file: ./drivers/scsi/mpi3mr/mpi3mr_app.c
the friend group, in full, no one left behind π«Ά:
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_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 page, bestie!! π this one came out of ./drivers/scsi/mpi3mr and it's dated October 2026 β so yeah, it's from the future and it still ate π go read the source, ily, bye π¦β¨
π¦ 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