STRUCT LEAPRAID_RAID_CFG_P0(9)
π struct leapraid_raid_cfg_p0(9) π
okay so bestie, welcome to the Kernel API Manual entry for struct leapraid_raid_cfg_p0 β yes the whole manual name is in the title, we're doing this properly β¨ this page is literally about RAID configuration page 0, and it's giving "table of contents but make it firmware" π
πΈ NAME πΈ
struct leapraid_raid_cfg_p0 β RAID configuration page 0 π
that's the whole vibe, that's the whole struct, no notes π«Ά
β SYNOPSIS β
here's the exact shape of it, no cap, copy it into ur brain exactly like this:
struct leapraid_raid_cfg_p0 {
struct leapraid_cfg_ext_pg_header header;
u8 r1[3];
u8 cfg_num;
u8 r2[32];
u8 elements_num;
u8 r3[3];
struct leapraid_raid_cfg_p0_element cfg_element[];
};
that trailing cfg_element[] is a flexible array member btw, it's the main character at the end of the struct π
π¦ Members π¦
okay so let's go member by member, every single one, we're not skipping ANY of them, that would be disrespectful to the struct π
headerβ the extended configuration page header. it's the little label on the front of the page, extended config page flavour specifically πr1β reserved. that's it, that's the whole job, it's just vibing there πcfg_numβ the configuration number. ur little ID badge number for this config πr2β reserved. (u8 r2[32]of pure "don't touch" energy, respect the space π)elements_numβ the number of RAID elements. how many besties are in thecfg_elementfriend group β¨r3β reserved. third reserved one, iconic consistency πcfg_elementβ array of RAID elements. this is where the actual RAID elements live,struct leapraid_raid_cfg_p0_elementsized, and it'selements_numof them long, iykyk π«Ά
ngl the reserved fields (r1,r2,r3) are reserved β that's the whole fact, don't go reading meaning into them π
π SEE ALSO π
the source of truth lives in the kernel file ./drivers/scsi/leapraid/leapraid.h β that's where all these structs and unions actually are, go look, it's fine, it's literally in the source tree π§
and here's the full friend list, every single one, in order, because we do NOT drop references on this page π
struct leapraid_reg_base(9)struct leapraid_atomic_req_desc(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)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)
fr fr bestie, that's the whole page. struct understood, reserved fields respected, references intact, vibes immaculate π
okay and for the cute sign-off moment: this one lives under ./drivers/scsi/leapraid, and the page is dated October 2026 β so yeah, future-dated manual page, main character energy for real πβ¨π slay, go read the header file π¦
π¦ 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