devl_resource_register(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, <rainbow>devl_resource_register</rainbow> β€” it's literally the devlink resource register function πŸ’… like, that's the whole vibe, that's the name, periodt ✨


✨ SYNOPSIS ✨

int devl_resource_register (struct devlink *devlink , const char
*resource_name , u64 resource_size , u64 resource_id , u64
parent_resource_id , const struct devlink_resource_size_params *params
);

like, look at her πŸ‘‘ six arguments, one int, no cap fr fr 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • devlink β€” the devlink πŸ¦‹ yep that's it, that's the whole description, she's self-explanatory iykyk
  • resource_name β€” the resource's name πŸ’– like what you're calling this thing
  • resource_size β€” the resource's size 🌸 how big it is, that's the tea
  • resource_id β€” the resource's id ⭐ her little number, her identifier, her whole identity
  • parent_resource_id β€” the resource's parent id 🌈 who she belongs to, the family tree situation
  • params β€” size parameters πŸŽ€ the parameters, specifically of the size variety

πŸ’œ DESCRIPTION πŸ’œ

so, the way that generic resources work 😭 bestie, they should reuse the same names across drivers β€” like, consistency is the moment, please don't make up a new name every single time, that's not the vibe check we're going for πŸ™ˆ

please see the generic resources list at:

Documentation/networking/devlink/devlink-resource.rst

literally go read it, it's giving required reading πŸ“– ✨


πŸ”₯ RETURN πŸ”₯

  • 0 on success πŸ‘‘ slay
  • a negative error code otherwise πŸ’€ not slay, but that's what you get

πŸ¦‹ SEE ALSO πŸ¦‹

go read all of them, i'm obsessed with a complete cross-reference list ngl πŸ’œ


okay that's the whole page bestie, mwah πŸ’‹ β€” this one's from ./net/devlink, dated October 2026, and it's devl_resource_register(9) if you needed the reminder, love u, go register some resources, bye πŸŽ€βœ¨

πŸ“¦ where this page comes from