STRUCT LEAPRAID_REP_DESC_SEG_MAINT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct leapraid_rep_desc_seg_maint(9) β€” the kernel API manual, bestie edition

okay so you're in the kernel API manual (section 9, the big-kid section) and the star of the show is struct leapraid_rep_desc_seg_maint β€” it's literally the struct that maintains reply descriptor segment memory. that's the whole job. it holds the segment, it holds where that segment lives in DMA-land, and it points back at the main reply descriptor structure. tiny struct, huge responsibility, main character energy fr fr 🌸


✨ SYNOPSIS ✨

here's the shape of it, copied exactly so you can trust me:

struct leapraid_rep_desc_seg_maint {
    void *rep_desc_seg;
    dma_addr_t rep_desc_seg_dma;
    struct leapraid_rep_desc_maint *rep_desc_maint;
 };

no cap, that's the whole struct. three fields. she's compact and she knows it πŸŽ€


πŸ¦‹ Members πŸ¦‹

  • rep_desc_seg β€” a pointer to the reply descriptor segment. yes, just a void *. it's giving "i contain multitudes" energy ✨
  • rep_desc_seg_dma β€” the DMA address of the reply descriptor segment, typed as a dma_addr_t. this is the address the hardware side cares about, iykyk πŸ’«
  • rep_desc_maint β€” a pointer to the main reply descriptor structure (struct leapraid_rep_desc_maint *). the little segment struct keeps a link back home to its parent 🫢

πŸ‘‘ SEE ALSO πŸ‘‘

bestie, the crossover episode is LONG and honestly iconic. all of these live in the kernel file ./drivers/scsi/leapraid/leapraid_func.h, and they're all siblings in the same driver family tree 🌈

  • struct leapraid_adapter_features(9)
  • struct leapraid_adapter_attr(9)
  • struct leapraid_io_req_tracker(9)
  • struct leapraid_task_tracker(9)
  • struct leapraid_rep_desc_maint(9)
  • struct leapraid_mem_desc(9)
  • enum LEAPRAID_CB_INDEX(9)
  • struct leapraid_default_reply(9)
  • struct leapraid_sense_buffer(9)
  • struct leapraid_driver_cmd(9)
  • struct leapraid_driver_cmds(9)
  • struct leapraid_dynamic_task_desc(9)
  • struct leapraid_fw_evt_work(9)
  • struct leapraid_fw_evt_struct(9)
  • struct leapraid_rq(9)
  • struct leapraid_int_rq(9)
  • struct leapraid_blk_mq_poll_rq(9)
  • struct leapraid_notification_desc(9)
  • struct leapraid_overheat_desc(9)
  • struct leapraid_reset_desc(9)
  • struct leapraid_scan_dev_desc(9)
  • struct leapraid_access_ctrl(9)
  • struct leapraid_fw_log_desc(9)
  • struct leapraid_card_port(9)
  • struct leapraid_card_phy(9)
  • struct leapraid_topo_node(9)
  • struct leapraid_dev_topo(9)
  • struct leapraid_boot_dev(9)
  • struct leapraid_boot_devs(9)
  • struct leapraid_adapter(9)
  • struct leapraid_enc_node(9)
  • struct leapraid_raid_volume(9)
  • struct leapraid_starget_priv(9)
  • struct leapraid_sdev_priv(9)
  • struct leapraid_sas_dev(9)
  • struct leapraid_sas_port(9)
  • struct leapraid_vphy(9)
  • struct leapraid_tgt_rst_list(9)
  • struct sense_info(9)
  • struct leapraid_fw_log_info(9)
  • enum reset_type(9)
  • struct leapraid_card_port_feature(9)

like i said. crossover episode. go read them, they ate πŸ’…

heads up bestie: they're all in ./drivers/scsi/leapraid/leapraid_func.h, so that's your one-stop shop if you wanna go source-diving 🧚

okay that's the page!! this one comes to you from ./drivers/scsi/leapraid, dated October 2026, and the page itself is struct leapr...sc_seg_maint(9) (the name got truncated by the formatter, not by me, don't come for me 😭). love u, go read your structs πŸ’–πŸ¦‹βœ¨

πŸ“¦ where this page comes from