STRUCT PDS_LM_CMD(9)
π struct pds_lm_cmd(9) π
okay so bestie, welcome to the Kernel API Manual β we're talking about struct pds_lm_cmd, and honestly? it's giving generic command. that's the whole vibe. it's the blueprint every command in this family gets stamped from, and yes we ARE going to read it together, don't scroll π
β¨ NAME β¨
struct pds_lm_cmd β literally just a generic command, no cap π
π¦ SYNOPSIS π¦
here's the whole girl, look at her:
struct pds_lm_cmd {
u8 opcode;
u8 rsvd;
__le16 vf_id;
u8 rsvd2[56];
};
she's 60 bytes of pure main character energy, and every field is doing its job πΈ
π MEMBERS π
breaking down the cast, one field at a time π«Ά
opcodeβ the opcode. this is the field that tells everyone which command this actually is. it's the personality, the moment, the whole point π₯rsvdβ word boundary padding. it's not here to be interesting, it's here to keep things lined up so the layout doesn't get messy. respect the padding tho πvf_idβ the VF id. that's the virtual function identifier, and it's an__le16, so little-endian besties only β¨rsvd2β structure padding to 60 Bytes. it'su8 rsvd2[56], and it exists purely to push the whole struct out to that 60-byte finish line. icon behavior π
ngl, like half this struct is padding. that's not a flaw, that's just how the layout slays π
π SEE ALSO π
the whole extended universe, fr fr β go read these next iykyk:
- Kernel file
./include/linux/pds/pds_adminq.hstruct 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_core_q_init_comp(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_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)
and that's the whole page bestie, you ate that π this one lives in ./include/linux/pds and it's dated October 2026 β see you in the next manpage, mwah ππ
π¦ 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