STRUCT PCI_DOE_TASK(9)

✨ NAME ✨

okay so bestie, this page is from the Kernel API Manual, and the main character is struct pci_doe_task(9) — it literally represents a single query/response. That’s the whole vibe: one task, one query/response moment, no cap. 💅

🌸 SYNOPSIS 🌸

struct pci_doe_task {
    struct pci_doe_feature feat;
    const __le32 *request_pl;
    size_t request_pl_sz;
    __le32 *response_pl;
    size_t response_pl_sz;
    int rv;
    void (*complete)(struct pci_doe_task *task);
    void *private;
    struct work_struct work;
    struct pci_doe_mb *doe_mb;
};

🎀 Members 🎀

• feat — DOE Feature
• request_pl — the request payload
• request_pl_sz — size of the request payload (bytes)
• response_pl — the response payload
• response_pl_sz — size of the response payload (bytes)
• rv — return value. Length of received response or error (bytes)
• complete — called when task is complete
• private — private data for the consumer
• work — used internally by the mailbox
• doe_mb — used internally by the mailbox

🦋 SEE ALSO 🦋

• Kernel file ./drivers/pci/doe.c
• struct pci_doe_mb(9)
• pci_doe_create_mb(9)
• pci_doe_destroy_mb(9)
• pci_doe_supports_feat(9)
• pci_doe_submit_task(9)
• pci_doe(9)
• pci_find_doe_mailbox(9)

bestie, that’s the whole page — every member, every reference, all accounted for. 🫶

💖 source/version: ./drivers/pci · date: October 2026 · page: struct pci_doe_task(9) — periodt. 🎀