ioc_reset_count_show(9)
π ioc_reset_count_show(9) β the kernel manual, but make it make sense
Hey bestie, welcome to the ioc_reset_count_show(9) page from the Kernel API Manual. Yes that's a mouthful, no I will not be shortening it. This is the whole vibe: a little sysfs show function that tells you about the ioc reset count. Let's get into it π«Ά
β¨ NAME β¨
ioc_reset_count_show β literally the ioc reset count. That's it. That's the name section. Iconic behavior honestly π
πΈ SYNOPSIS πΈ
ssize_t ioc_reset_count_show (struct device *cdev , struct
device_attribute *attr , char *buf );
That's the signature, copied exactly, do not come for me about the spacing π
π¦ ARGUMENTS π¦
cdevβ pointer to embedded class device. Your device-y entry point, main character energy.attrβ?β¦ yeah. That's what the page says. A whole question mark. The docs simply did not know and honestly? Respect for the honesty πbufβ the buffer returned. This is where the output goes, it's giving delivery slot π¦
π DESCRIPTION π
So what does this thing actually do? This is firmware queue depth limit.
Lowkey that is the entire description. It's also a sysfs 'read-only' shost attribute β so read it, love it, admire it, but you're not writing to it, bestie. No cap π₯
π SEE ALSO π
Bestie the cross-reference list here is long long. Buckle up, we're listing every single one, fr fr. First up, the kernel file they live in: ./drivers/scsi/mpt3sas/mpt3sas_ctl.c.
enum block_state(9)_ctl_display_some_debug(9)mpt3sas_ctl_done(9)_ctl_check_event_type(9)mpt3sas_ctl_add_to_event_log(9)mpt3sas_ctl_event_callback(9)_ctl_verify_adapter(9)mpt3sas_ctl_pre_reset_handler(9)mpt3sas_ctl_clear_outstanding_ioctls(9)mpt3sas_ctl_reset_done_handler(9)_ctl_fasync(9)_ctl_poll(9)_ctl_set_task_mid(9)_ctl_send_mctp_passthru_req(9)_ctl_do_mpt_command(9)_ctl_getiocinfo(9)_ctl_eventquery(9)_ctl_eventenable(9)_ctl_eventreport(9)_ctl_do_reset(9)_ctl_btdh_search_sas_device(9)_ctl_btdh_search_pcie_device(9)_ctl_btdh_search_raid_device(9)_ctl_btdh_mapping(9)_ctl_diag_capability(9)_ctl_diag_get_bufftype(9)_ctl_diag_register_2(9)mpt3sas_enable_diag_buffer(9)_ctl_diag_register(9)_ctl_diag_unregister(9)_ctl_diag_query(9)mpt3sas_send_diag_release(9)_ctl_diag_release(9)_ctl_diag_read_buffer(9)_ctl_addnl_diag_query(9)_ctl_enable_diag_sbr_reload(9)_ctl_compat_mpt_command(9)_ctl_ioctl_main(9)_ctl_get_mpt_mctp_passthru_adapter(9)mpt3sas_get_device_count(9)_ctl_ioctl(9)_ctl_mpt2_ioctl(9)_ctl_ioctl_compat(9)_ctl_mpt2_ioctl_compat(9)version_fw_show(9)version_bios_show(9)version_mpi_show(9)version_product_show(9)version_nvdata_persistent_show(9)version_nvdata_default_show(9)board_name_show(9)board_assembly_show(9)board_tracer_show(9)io_delay_show(9)device_delay_show(9)fw_queue_depth_show(9)host_sas_address_show(9)logging_level_show(9)fwfault_debug_show(9)reply_queue_count_show(9)BRM_status_show(9)host_trace_buffer_size_show(9)host_trace_buffer_show(9)host_trace_buffer_enable_show(9)diag_trigger_master_show(9)diag_trigger_master_store(9)diag_trigger_event_show(9)diag_trigger_event_store(9)diag_trigger_scsi_show(9)diag_trigger_scsi_store(9)diag_trigger_mpi_show(9)diag_trigger_mpi_store(9)drv_support_bitmap_show(9)enable_sdev_max_qd_show(9)enable_sdev_max_qd_store(9)sas_address_show(9)sas_device_handle_show(9)sas_ncq_prio_supported_show(9)sas_ncq_prio_enable_show(9)mpt3sas_ctl_init(9)mpt3sas_ctl_release(9)mpt3sas_ctl_exit(9)
Like I said. Long long. But you have them all now, so go be curious π
That's the whole page bestie β no options list, no exit statuses, no environment variables, just the reset count and a truly enormous friend group β¨
And that's a wrap! π This one came from ./drivers/scsi/mpt3sas, dated October 2026 β go forth and read your sysfs attributes responsibly, 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