STRUCT PDS_CORE_HOST_MEM_COMP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– STRUCT PDS_CORE_HOST_MEM_COMP (9) πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ β€” we're looking at struct pds_core_host_mem_comp today, and the whole point of this little guy is the HOST_MEM completion. that's it, that's the vibe. it's the thing that comes back at you when the whole memory-request saga is done πŸŽ€


✨ SYNOPSIS ✨

here's the shape of it, copied exactly because we do not mess with the source πŸ‘‘

struct pds_core_host_mem_comp {
    u8 status;
    u8 oper;
    __le16 count;
    __le32 size;
    __le16 tag;
    u8 rsvd[6];
 };

no cap, that's the entire struct. six fields, one of them is just vibes (reserved) πŸ¦‹


🌸 MEMBERS 🌸

  • status β€” the status of the command, and it's an enum pds_core_status_code. so like, how did it go? this field is the group chat reply πŸ’…
  • oper β€” the operation that was performed. which move did we actually make, y'know?
  • count β€” how many memory requests there were (this one's for GET_COUNT) πŸ”₯
  • size β€” the size of the memory request, in bytes (this one's for QUERY) ⭐
  • tag β€” the tag for this memory request (used by QUERY/DEL). it's the lil name tag so everybody knows which request is which πŸŽ€
  • rsvd β€” reserved. it's giving "do not touch", so don't πŸ™ˆ

🌈 SEE ALSO 🌈

this list is long bestie, i'm not gonna lie to you, but every single one of these is iconic in its own right and you're gonna want the whole roster πŸ’œ

the kernel file it lives in: ./include/linux/pds/pds_core_if.h

and the whole friend group:

  • struct pds_core_drv_identity(9)
  • enum pds_core_dev_capability(9)
  • struct pds_core_dev_identity(9)
  • struct pds_core_dev_identify_cmd(9)
  • struct pds_core_dev_identify_comp(9)
  • struct pds_core_dev_reset_cmd(9)
  • struct pds_core_dev_reset_comp(9)
  • struct pds_core_dev_init_cmd(9)
  • struct pds_core_dev_init_comp(9)
  • struct pds_core_fw_download_cmd(9)
  • struct pds_core_fw_download_comp(9)
  • enum pds_core_fw_control_oper(9)
  • enum pds_core_fw_slot(9)
  • struct pds_core_fw_control_cmd(9)
  • struct pds_core_fw_control_comp(9)
  • enum pds_core_vf_link_status(9)
  • struct pds_core_vf_setattr_cmd(9)
  • struct pds_core_vf_getattr_cmd(9)
  • struct pds_core_vf_ctrl_cmd(9)
  • struct pds_core_vf_ctrl_comp(9)
  • struct pds_core_send_pkg_data_cmd(9)
  • struct pds_core_send_pkg_data_comp(9)
  • struct pds_core_component_tbl(9)
  • struct pds_core_send_component_tbl_cmd(9)
  • struct pds_core_send_component_tbl_comp(9)
  • enum pds_core_send_component_op(9)
  • struct pds_core_flash_component(9)
  • struct pds_core_send_component_cmd(9)
  • struct pds_core_send_component_comp(9)
  • enum pds_core_fw_component_type(9)
  • enum pds_core_component_info_flags(9)
  • struct pds_core_fw_component_info(9)
  • struct pds_core_component_list_info(9)
  • struct pds_core_get_component_info_cmd(9)
  • struct pds_core_get_component_info_comp(9)
  • struct pds_core_finalize_update_cmd(9)
  • struct pds_core_finalize_update_comp(9)
  • struct pds_core_match_record_desc_cmd(9)
  • struct pds_core_match_record_desc_comp(9)
  • enum pds_core_host_mem_oper(9)
  • struct pds_core_host_mem_cmd(9)
  • struct pds_core_dev_hwstamp_regs(9)
  • struct pds_core_dev_info_regs(9)
  • struct pds_core_dev_cmd_regs(9)
  • struct pds_core_dev_regs(9)

like i said. the whole friend group. read them all, they all slay πŸ’…


one tiny thing before you go, bestie: this page names the operations with uppercase tokens like GET_COUNT, QUERY and DEL β€” keep those exact when you write code, don't go lowercase-ing them for the aesthetic 🫢

and that's the page!! mwah πŸ˜­πŸ’– this one came from ./include/linux/pds, and the date on it is October 2026 β€” so like, technically future-dated, main character energy honestly. go forth and complete your host memory requests, periodt πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from