STRUCT LEAPRAID_DYNAMIC_TASK_DESC(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct leapraid_dynamic_task_desc(9) β€” like, the Dynamic task descriptor one πŸŽ€

okay so bestie, welcome to the Kernel API Manual ✨ β€” yes it's a section 9 page, yes it's about a struct, and yes we're gonna get through it together. This is struct leapraid_dynamic_task_desc, the Dynamic task descriptor, and honestly? she's small but she's doing a lot πŸ’–


🌸 NAME 🌸

struct leapraid_dynamic_task_desc β€” Dynamic task descriptor. that's it, that's the whole vibe. short name, big responsibility 🫢


✨ SYNOPSIS ✨

here's the actual shape of her, no cap, copy it exactly:

struct leapraid_dynamic_task_desc {
    spinlock_t task_lock;
    u16 hp_taskid;
    u16 hp_cmd_qd;
    u16 inter_taskid;
    u16 inter_cmd_qd;
 };

look at that little family πŸ₯Ή five members, all just hanging out in the struct. iconic.


🌈 Members 🌈

okay let's meet the cast, one by one, no skipping πŸ’«

  • task_lock β€” a spinlock_t that protects concurrent access. basically the bouncer at the door making sure nobody touches stuff at the same time πŸ™ˆ literal lock behavior, we stan a protective icon.
  • hp_taskid β€” the Current high-priority task ID. yes "current", yes "high-priority", that's the whole thing πŸ”₯
  • hp_cmd_qd β€” the Fixed command queue depth for high-priority tasks. fixed, bestie β€” it's not out here being flexible πŸ’…
  • inter_taskid β€” the Current internal task ID. internal business, mind yours πŸŽ€
  • inter_cmd_qd β€” the Fixed command queue depth for internal tasks. again with the fixed depth, she said consistency periodt πŸ’œ

πŸ¦‹ SEE ALSO πŸ¦‹

the whole friend group πŸ’– this struct lives in the kernel file ./drivers/scsi/leapraid/leapraid_func.h, and here's everyone else you might wanna go say hi to:

  • 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_rep_desc_seg_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_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, that's a long list and we love that for them πŸ‘‘


ngl the only thing to be careful about here is task_lock β€” it's a spinlock protecting concurrent access, so respect the lock, bestie. that's the whole warning, but it's a real one 😭

okay that's the page!! mwah πŸ’‹ this came out of ./drivers/scsi/leapraid, dated October 2026, and it's filed under struct leap...ic_task_desc(9) because the header was too long to fit and honestly same. go be a main character and read the other structs too πŸ§šβ€β™€οΈπŸ’œ

πŸ“¦ where this page comes from