STRUCT LEAPRAID_ATOMIC_REQ_DESC(9)
πΈ NAME πΈ
ok so welcome to the Kernel API Manual, bestie π β today's main character is struct leapraid_atomic_req_desc, aka the Atomic request descriptor. that's it, that's the whole vibe. it's a little struct with big responsibilities. periodt.
β¨ SYNOPSIS β¨
like, here's the whole thing, no gatekeeping:
struct leapraid_atomic_req_desc {
u8 flg;
u8 msix_idx;
__le16 taskid;
};
three members. tiny. iconic. π
π¦ Members π¦
okay let's meet the cast π
flgβ the descriptor flag that says what kind of request this is (think SCSI I/O and friends). it's giving "what's my purpose" energy. πmsix_idxβ the MSI-X vector index, aka which door the interrupt knocks on. routing, but make it fashion. β¨taskidβ the unique task identifier tied to this request, so everybody knows exactly which task is which. no cap, no mix-ups. π
π SEE ALSO π
the whole friend group π«Ά β this struct literally lives in the kernel file ./drivers/scsi/leapraid/leapraid.h, and here's everybody else you might want to go say hi to:
struct leapraid_reg_base(9)union leapraid_rep_desc_union(9)struct leapraid_req(9)struct leapraid_rep(9)struct leapraid_sge_simple32(9)struct leapraid_sge_simple64(9)struct leapraid_sge_simple_union(9)struct leapraid_sge_chain_union(9)struct leapraid_ieee_sge_simple32(9)struct leapraid_ieee_sge_simple64(9)union leapraid_ieee_sge_simple_union(9)union leapraid_ieee_sge_chain_union(9)struct leapraid_chain64_ieee_sg(9)union leapraid_ieee_sge_io_union(9)union leapraid_simple_sge_union(9)union leapraid_sge_io_union(9)struct leapraid_cfg_pg_header(9)struct leapraid_cfg_ext_pg_header(9)struct leapraid_cfg_req(9)struct leapraid_cfg_rep(9)struct leapraid_boot_dev_format_sas_wwid(9)struct leapraid_boot_dev_format_enc_slot(9)struct leapraid_boot_dev_format_dev_name(9)union leapraid_boot_dev_format(9)struct leapraid_manufacturing_p0(9)struct leapraid_bios_page2(9)struct leapraid_bios_page3(9)struct leapraid_raidvol0_phys_disk(9)struct leapraid_raidvol_p0(9)struct leapraid_raidvol_p1(9)struct leapraid_raidpd_p0(9)struct leapraid_sas_io_unit0_phy_info(9)struct leapraid_sas_io_unit_p0(9)struct leapraid_exp_p0(9)struct leapraid_exp_p1(9)struct leapraid_sas_dev_p0(9)struct leapraid_sas_phy_p0(9)struct leapraid_enc_p0(9)struct leapraid_raid_cfg_p0_element(9)struct leapraid_raid_cfg_p0(9)union leapraid_mpi_scsi_io_cdb_union(9)struct leapraid_mpi_scsiio_req(9)union leapraid_scsi_io_cdb_union(9)struct leapraid_scsiio_req(9)struct leapraid_scsiio_rep(9)struct leapraid_scsi_tm_req(9)struct leapraid_scsi_tm_rep(9)struct leapraid_sep_req(9)struct leapraid_sep_rep(9)struct leapraid_adapter_init_req(9)struct leapraid_rep_desc_q_arr(9)struct leapraid_adapter_init_rep(9)struct leapraid_adapter_log_req(9)struct leapraid_adapter_log_rep(9)struct leapraid_adapter_features_req(9)struct leapraid_adapter_features_rep(9)struct leapraid_scan_dev_req(9)struct leapraid_scan_dev_rep(9)struct leapraid_evt_notify_req(9)struct leapraid_evt_notify_rep(9)struct leapraid_evt_data_sas_dev_status_change(9)struct leapraid_evt_data_ir_change(9)struct leapraid_evt_data_sas_disc(9)struct leapraid_evt_sas_topo_phy_entry(9)struct leapraid_evt_data_sas_topo_change_list(9)struct leapraid_evt_data_sas_enc_dev_status_change(9)struct leapraid_io_unit_ctrl_req(9)struct leapraid_io_unit_ctrl_rep(9)struct leapraid_raid_act_req(9)struct leapraid_raid_act_rep(9)struct leapraid_smp_passthrough_req(9)struct leapraid_smp_passthrough_rep(9)struct leapraid_sas_io_unit_ctrl_req(9)
yup, all of them. every single one. we don't skip the boring parts in this house π
and that's the whole page, bestie π§ β this one came straight out of ./drivers/scsi/leapraid, dated October 2026 for the Kernel API Manual. go forth and describe your atomic requests with main character energy. 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