STRUCT DEVLINK_DPIPE_HEADER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the struct devlink_dpipe_header(9) page β€” it's a Kernel API Manual situation and honestly it's giving "small struct, big responsibilities" ✨


🌸 NAME 🌸

struct devlink_dpipe_header β€” the dpipe header object, periodt. That's literally it, that's the whole vibe πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

struct devlink_dpipe_header {
    const char *name;
    unsigned int id;
    struct devlink_dpipe_field *fields;
    unsigned int fields_count;
    bool global;
 };

no cap, that's the entire struct β€” five members, all iconic in their own way πŸ‘‘


πŸŽ€ Members πŸŽ€

okay so let's do a little member-by-member vibe check, one at a time, no skipping 🫢

  • name β€” the header name πŸ’« lowkey self-explanatory but yes, this is what the header is called.
  • id β€” the index, bestie. and listen, whether it's global or local is determined by the global bit β€” they're linked like that, iykyk πŸ”₯
  • fields β€” the fields. that's it. that's the description. the fields are fields πŸ’€ (she's a pointer to struct devlink_dpipe_field, in case the synopsis didn't already spoil it for you).
  • fields_count β€” the number of fields 🌸 like, how many of them there are. very demure, very mindful counting.
  • global β€” this one's the main character πŸ‘‘ it indicates if the header is shared like most protocol headers, or if it's driver specific. literally the whole global-vs-driver-specific distinction lives in this one bool and I'm obsessed.
ngl the fields one being described as just "fields" is so real of the kernel docs 😭 but we respect her, she ate.

⭐ SEE ALSO ⭐

okay this list is LONG and we're listing every single one because nobody gets left out on my watch πŸ’…

Kernel file: ./include/net/devlink.h

  • struct devlink_port_pci_pf_attrs(9)
  • struct devlink_port_pci_vf_attrs(9)
  • struct devlink_port_pci_sf_attrs(9)
  • struct devlink_port_attrs(9)
  • struct devlink_linecard_ops(9)
  • struct devlink_dpipe_field(9)
  • struct devlink_dpipe_match(9)
  • struct devlink_dpipe_action(9)
  • struct devlink_dpipe_value(9)
  • struct devlink_dpipe_entry(9)
  • struct devlink_dpipe_dump_ctx(9)
  • struct devlink_dpipe_table(9)
  • struct devlink_dpipe_table_ops(9)
  • struct devlink_dpipe_headers(9)
  • struct devlink_resource_size_params(9)
  • struct devlink_flash_notify(9)
  • struct devlink_param(9)
  • struct devlink_flash_update_params(9)
  • struct devlink_region_ops(9)
  • struct devlink_port_region_ops(9)
  • struct devlink_health_reporter_ops(9)
  • struct devlink_trap_metadata(9)
  • struct devlink_trap_policer(9)
  • struct devlink_trap_group(9)
  • struct devlink_trap(9)
  • struct devlink_port_ops(9)

like, that's the whole devlink extended fam right there 🌈 go read them all, I'll wait 🧚


and that's the page! this one came from ./include/net, dated October 2026, and it's the struct devlink_dpipe_header(9) page of the Kernel API Manual β€” slay, bye bestie πŸ’œπŸŽ€

πŸ“¦ where this page comes from