complete_cmd_fusion(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– complete_cmd_fusion(9) πŸ’–

okay so real talk: you're in the Kernel API Manual, section 9, and the star of this page is complete_cmd_fusion. yes she has a whole page. yes she earned it. πŸŽ€


✨ NAME ✨

complete_cmd_fusion β€” literally just completes command. that's it. that's the whole job description. iconic minimalism ngl πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int complete_cmd_fusion (struct megasas_instance *instance , u32
MSIxIndex , struct megasas_irq_context *irq_context );

she takes three things and hands you back an int. short signature, big main character energy ✨


🌸 ARGUMENTS 🌸

  • instance β€” Adapter soft state. like, the whole adapter's personality/vibes, stored in one struct 🫢
  • MSIxIndex β€” MSI number. which interrupt lane we're dealing with, bestie πŸ”₯
  • irq_context β€” IRQ context. the interrupt's little backpack of context, carried along for the ride πŸŽ’

πŸ’œ DESCRIPTION πŸ’œ

Completes all commands that is in reply descriptor queue. not some of them. not "the ones that look cute". all of them. every single reply descriptor sitting in that queue gets completed, periodt πŸ‘‘

like she's doing a group-chat cleanup: everyone gets their reply, no one gets left on read πŸ’–


🌈 SEE ALSO 🌈

first up, the kernel file where all this lives:

Kernel file ./drivers/scsi/megaraid/megaraid_sas_fusion.c

and the whole friend group β€” say hi to all of them, there are a LOT and every single one counts 🧚:

megasas_adp_reset_wait_for_ready(9), megasas_check_same_4gb_region(9),
megasas_enable_intr_fusion(9), megasas_disable_intr_fusion(9),
megasas_get_cmd_fusion(9), megasas_return_cmd_fusion(9),
megasas_write_64bit_req_desc(9), megasas_fire_cmd_fusion(9),
megasas_fusion_update_can_queue(9), megasas_free_cmds_fusion(9),
megasas_create_sg_sense_fusion(9), megasas_alloc_cmds_fusion(9),
wait_and_poll(9), megasas_ioc_init_fusion(9),
megasas_sync_pd_seq_num(9), megasas_allocate_raid_maps(9),
megasas_configure_queue_sizes(9), megasas_free_ioc_init_cmd(9),
megasas_init_adapter_fusion(9), megasas_fault_detect_work(9),
map_cmd_status(9), megasas_is_prp_possible(9), megasas_make_prp_nvme(9),
megasas_make_sgl_fusion(9), megasas_make_sgl(9), megasas_set_pd_lba(9),
megasas_stream_detect(9), megasas_set_raidflag_cpu_affinity(9),
megasas_build_ldio_fusion(9), megasas_build_ld_nonrw_fusion(9),
megasas_build_syspd_fusion(9), megasas_build_io_fusion(9),
megasas_build_and_issue_cmd_fusion(9), megasas_complete_r1_command(9),
access_irq_context(9), release_irq_context(9),
megasas_enable_irq_poll(9), megasas_sync_irqs(9), megasas_irqpoll(9),
megasas_complete_cmd_dpc_fusion(9), megasas_isr_fusion(9),
build_mpt_mfi_pass_thru(9), build_mpt_cmd(9),
megasas_issue_dcmd_fusion(9), megasas_release_fusion(9),
megasas_read_fw_status_reg_fusion(9),
megasas_alloc_host_crash_buffer(9), megasas_free_host_crash_buffer(9),
megasas_adp_reset_fusion(9), megasas_check_reset_fusion(9),
megasas_trigger_snap_dump(9), megasas_tm_response_code(9),
megasas_issue_tm(9)

iykyk 😭 that's the whole extended fam, go read their pages too fr fr πŸ’€

lowkey a reminder: this page is in the Kernel API Manual, source dir ./drivers/scsi/megaraid, dated October 2026 β€” and yes, the manual name being the same as the title is just how section 9 rolls, don't come for her πŸ™ˆ

and that's the tea, bestie πŸ“ hope the queue is empty and your interrupts are cozy. stay slay, ship good code πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«Ά

πŸ“¦ where this page comes from