DPNI_FS_OPT...TASH_CONTROL(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… DPNI_FS_OPT_SET_STASH_CONTROL πŸ’…

Okay bestie, welcome to the Kernel API Manual β€” we're looking at DPNI_FS_OPT_SET_STASH_CONTROL today and it's giving very specific bit-field energy. ✨


🌸 NAME 🌸

DPNI_FS_OPT_SET_STASH_CONTROL β€” this one indicates whether the 6 lowest significant bits of FLC are used for stash control. No cap, that's the whole mood. πŸ’–

When this flag is set, the 6 least significant bits in value are interpreted like this:

  • bits 0-1 β€” tells you the number of 64 byte units of context that are stashed. In this case, the FLC value is interpreted as a memory address, excluding the 6 LS bits.
  • bits 2-3 β€” tells you the number of 64 byte units of frame annotation to be stashed. Annotation is placed at FD[ADDR].
  • bits 4-5 β€” tells you the number of 64 byte units of frame data to be stashed. Frame data is placed at FD[ADDR] + FD[OFFSET].

And listen, bestie: this flag is ignored if DPNI_FS_OPT_SET_FLC is not specified. That's the rule, periodt. πŸ’€


✨ SYNOPSIS ✨

DPNI_FS_OPT_SET_STASH_CONTROL

Lowkey just the one symbol, bestie. 🫢


πŸ¦‹ SEE ALSO πŸ¦‹

Okay, the SEE ALSO roster is massive, and every single one is invited to the group chat. πŸ’–


mwah πŸ’‹ β€” source/version: ./drivers/net/ethernet/freesca...; date: October 2026; and yes, this is the DPNI_FS_OPT...TASH_CONTROL(9) page. Bye bestie 🫢

πŸ“¦ where this page comes from