ice_devlink_port_split(9)

📦 version 7.3.1, in nixpkgs unstable

Kernel API Manual · section 9, bestie 💅

🌸 NAME 🌸

ice_devlink_port_split — the .port_split devlink handler, and yes she's the main character of this particular port situation 🎀

🦋 SYNOPSIS 🦋

int ice_devlink_port_split (struct devlink *devlink , struct
       devlink_port *port , unsigned int count , struct netlink_ext_ack *extack
       );

💖 ARGUMENTS 💖

  • devlink — the devlink instance structure itself, the whole vibe container ✨
  • port — the devlink port structure, aka the port we're doing this to 🫶
  • count — how many ports you wanna split to, literally just the number 🔢
  • extack — the extended netdev ack structure, for the receipts ngl 📨

🌈 DESCRIPTION 🌈

So this is the callback for the devlink .port_split operation. That's the whole job description, periodt 👑

But okay, here's the lowkey tragic part: the devlink expression of available options is limited to just a number. That's it. Just a number. No extra flair, no vibes, nothing 😭 So what this function does is go search for an FW port option that supports the specified number. Like, hunting for the one that matches, iykyk 🔍

And because there could be multiple FW port options with the same port split count (yes, several, it's giving options on options), it allows switching between them. So when the same port split count request is issued again, it switches to the next FW port option with the same port split count. Round and round, one after another, she keeps it moving 💫

No cap, that number-only situation is legit just how devlink expresses available options — nothing deeper to read into it 🙈

⭐ RETURN ⭐

Zero on success, or an error code on failure. Slay on success, sad little error code otherwise 💀

💜 SEE ALSO 💜

Kernel file: ./drivers/net/ethernet/intel/ice/devlink/port.c

Okay that's the whole page, bestie — sourced from ./drivers/net/ethernet/intel/i... and dated October 2026, so go forth and split those ports responsibly 💅✨🎀

📦 where this page comes from