STRUCT PDS_CORE_Q_INIT_COMP(9)
π struct pds_core_q_init_comp(9) β Kernel API Manual π
okay bestie, so this is a page straight out of the Kernel API Manual and it's all about struct pds_core_q_init_comp β the completion that comes back at you when a queue init command finishes. lowkey it's the "we're done here β¨" receipt for queue setup, and honestly? it ate.
β¨ NAME β¨
struct pds_core_q_init_comp β Queue init command completion π¦
πΈ SYNOPSIS πΈ
the whole struct, exactly as it lives, no cap:
struct pds_core_q_init_comp {
u8 status;
u8 rsvd;
__le16 comp_index;
__le32 hw_index;
u8 hw_type;
u8 rsvd2[6];
u8 color;
};
π Members π
okay so each field, one by one, main character energy each:
statusβ the status of the command (it's anenum pds_core_status_code, iykyk). this is the vibe check of whether your command worked πrsvdβ word boundary padding. it's just there to keep things aligned, not doing anything, living its best filler-episode life πcomp_indexβ the index in the descriptor ring for which this is the completion π« like "hey, this one's done"hw_indexβ the Hardware Queue ID π₯hw_typeβ the Hardware Queue type πrsvd2β word boundary padding again (yes, a whole array of it,rsvd2[6], padding but make it fashion) β¨colorβ Color π literally just that, color
π«Ά SEE ALSO π«Ά
the whole friend group, all here, all iconic β plus where it actually lives:
- Kernel file
./include/linux/pds/pds_adminq.hstruct
and the extended fam:
pds_core_notifyq_event(9)struct pds_core_link_change_event(9)struct pds_core_reset_event(9)struct pds_core_client_event(9)struct pds_core_notifyq_cmd(9)struct pds_core_client_reg_cmd(9)struct pds_core_client_reg_comp(9)struct pds_core_client_unreg_cmd(9)struct pds_core_client_request_cmd(9)enum pds_core_logical_qtype(9)union pds_core_lif_config(9)struct pds_core_lif_status(9)struct pds_core_lif_info(9)struct pds_core_lif_identity(9)struct pds_core_lif_identify_cmd(9)struct pds_core_lif_identify_comp(9)struct pds_core_lif_init_cmd(9)struct pds_core_lif_init_comp(9)struct pds_core_lif_reset_cmd(9)enum pds_core_lif_attr(9)struct pds_core_lif_setattr_cmd(9)struct pds_core_lif_setattr_comp(9)struct pds_core_lif_getattr_cmd(9)struct pds_core_lif_getattr_comp(9)struct pds_core_q_identity(9)struct pds_core_q_identify_cmd(9)struct pds_core_q_identify_comp(9)struct pds_core_q_init_cmd(9)struct pds_vdpa_cmd(9)struct pds_vdpa_init_cmd(9)struct pds_vdpa_ident(9)struct pds_vdpa_ident_cmd(9)struct pds_vdpa_status_cmd(9)enum pds_vdpa_attr(9)struct pds_vdpa_setattr_cmd(9)struct pds_vdpa_vq_init_cmd(9)struct pds_vdpa_vq_init_comp(9)struct pds_vdpa_vq_reset_cmd(9)struct pds_vdpa_vq_reset_comp(9)struct pds_vdpa_set_features_cmd(9)struct pds_lm_cmd(9)struct pds_lm_state_size_cmd(9)struct pds_lm_state_size_comp(9)struct pds_lm_suspend_cmd(9)struct pds_lm_suspend_status_cmd(9)struct pds_lm_resume_cmd(9)struct pds_lm_sg_elem(9)struct pds_lm_save_cmd(9)struct pds_lm_restore_cmd(9)union pds_lm_dev_state(9)struct pds_lm_dirty_region_info(9)struct pds_lm_dirty_status_cmd(9)enum pds_lm_dirty_bmp_type(9)struct pds_lm_dirty_status_comp(9)struct pds_lm_dirty_enable_cmd(9)struct pds_lm_dirty_disable_cmd(9)struct pds_lm_dirty_seq_ack_cmd(9)struct pds_lm_host_vf_status_cmd(9)struct pds_fwctl_cmd(9)struct pds_fwctl_comp(9)struct pds_fwctl_ident_cmd(9)struct pds_fwctl_ident(9)struct pds_fwctl_query_cmd(9)struct pds_fwctl_query_comp(9)struct pds_fwctl_query_data_endpoint(9)struct pds_fwctl_query_data_operation(9)struct pds_fwctl_query_data(9)struct pds_fwctl_rpc_cmd(9)struct pds_sg_elem(9)struct pds_fwctl_rpc_comp(9)
ngl bestie, read every one of those before you go poking at queue init completions β the whole fam is doing lore together and you don't wanna miss a chapter π
and that's the page!! mwah π it ships from ./include/linux/pds, dated October 2026, and it's filed under struct pds_core_q_init_comp(9) β go forth and slay your queue inits, periodt ππ§ββοΈ
π¦ 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