reply_qfull_count_show(9)
β¨ reply_qfull_count_show(9) β¨
okay so you're reading the Kernel API Manual and this page is literally just about showing off the reply qfull count π it's a sysfs show callback bestie, it's not that deep, but let's give it the respect it deserves π«Ά
πΈ NAME πΈ
reply_qfull_count_show β Show reply qfull count β¨ (yes that's the whole name, no crumbs)
π SYNOPSIS π
ssize_t reply_qfull_count_show (struct device *dev , struct
device_attribute *attr , char *buf );
look at her. so simple. so iconic. π
π¦ ARGUMENTS π¦
devβ class device π» this is the device handing you the whole situationattrβ Device attributes π·οΈ the attribute vibes involvedbufβ Buffer to copy π₯ where the output string goes to live its life
π DESCRIPTION π
okay so the way this works: it retrieves the current value of the reply_qfull_count from the mrioc structure and formats it as a string for display β¨ that's it. that's the function. it's giving "just here to report the numbers" energy and honestly? we love a low-drama icon π
no cap, it's a tiny little getter-and-formatter and it ate π
β RETURN β
returns sysfs_emit return π― (that's the value, fr fr β it hands back whatever the emit gave it)
π SEE ALSO π
first up, the source file this whole thing calls home:
- Kernel file
./drivers/scsi/mpi3mr/mpi3mr_app.cπ
and now the full bestie list, all of them (9) pages, in the exact order the manpage gave them π«Ά:
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_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)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, that's a whole friend group and this page is proud of every single one π
ngl bestie, there's no bugs, no warnings, no env vars, no exit statuses on this page β just vibes, a struct field, and a sysfs_emit π§ it's giving "short and sweet" and we're not mad at it π
and that's the tea β this whole page lives under ./drivers/scsi/mpi3mr (that's the source), stamped October 2026 (that's the version date), and it's reply_qfull_count_show(9) all the way down π« bye bestie, go read your sysfs files responsibly πβ¨
π¦ 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