STRUCT ADF_GEN6_TL_CMDQ_DATA_REGS(9)
π 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
- 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