STRUCT ADF_GEN6_TL_CMDQ_DATA_REGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

struct adf_gen6_tl_cmdq_data_regs β€” the hardware CMDQ data, and it's literally populated by firmware. Like, FW does the homework and this struct is where the answers live. periodt.


✨ SYNOPSIS ✨

struct adf_gen6_tl_cmdq_data_regs {
    __u32 reg_tm_cmdq_wait_cnt;
    __u32 reg_tm_cmdq_exec_cnt;
    __u32 reg_tm_cmdq_drain_cnt;
    __u32 reserved;
 };

okay so it's four __u32 fields, that's the whole vibe, no cap. 🫢


πŸŽ€ Members πŸŽ€

  • reg_tm_cmdq_wait_cnt β€” the CMDQ wait count. that's it, that's the field. it's giving "waiting room energy". πŸ’…
  • reg_tm_cmdq_exec_cnt β€” the CMDQ execution count. the main character of the counter trio ngl. πŸ”₯
  • reg_tm_cmdq_drain_cnt β€” the CMDQ drain count. drain era, we love to see it. πŸŒ€
  • reserved β€” it's reserved, bestie. the manpage says absolutely nothing else about it and honestly? respect. let it be mysterious. πŸ™ˆ
fr fr just copying the field names over, do NOT go renaming these or reordering them β€” the firmware put them there on purpose. 😭

🌈 SEE ALSO 🌈

  • the kernel file ./drivers/crypto/intel/qat/qat_common/adf_gen6_tl.h β€” go read it, it's the source of truth πŸ’–
  • struct adf_gen6_tl_slice_data_regs(9)
  • struct adf_gen6_tl_device_data_regs(9)
  • struct adf_gen6_tl_ring_pair_data_regs(9)
  • struct adf_gen6_tl_layout(9)

it's giving a whole friend group of structs and this one is absolutely in it. iykyk πŸ¦‹


that's the whole page!! published in October 2026 as part of the Kernel API Manual, brought to you by ./drivers/crypto/intel/qat/qat... β€” mwah, stan the kernel docs team, they ate πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from