STRUCT NFP_BPF_REG_STATE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual ✨ like literally the kernel docs but make it cute. today's main character is struct nfp_bpf_reg_state, and she's here to hold register state for calls. no cap, that's the whole vibe πŸ’…


πŸŽ€ NAME πŸŽ€

struct nfp_bpf_reg_state β€” register state for calls 🫢 that's it, that's the job, and she does it flawlessly.


🌸 SYNOPSIS 🌸

struct nfp_bpf_reg_state {
    struct bpf_reg_state reg;
    bool var_off;
};

two members, zero drama, we love a minimal icon πŸ‘‘


πŸ¦‹ MEMBERS πŸ¦‹

  • reg β€” BPF register state from latest path ✨ like, the most recent path's register state, that's the one she's keeping track of, periodt.
  • var_off β€” for stack arg - changes stack offset on different paths 🌈 so when it's a stack arg and the stack offset shifts depending on which path you went down, this lil bool is the one who knows about it. iykyk.
fr fr that's every field. i checked twice. nothing hiding in there πŸ™ˆ

🌈 SEE ALSO 🌈

okay so these are the other kernel-file besties she hangs out with, all from ./drivers/net/ethernet/netronome/nfp/bpf/main.h:

  • struct nfp_app_bpf(9)
  • struct nfp_bpf_map(9)
  • struct nfp_insn_meta(9)
  • struct nfp_bpf_subprog_info(9)
  • struct nfp_prog(9)
  • struct nfp_bpf_vnic(9)

πŸ¦‹ and that's the whole page, bestie. source path was giving ./drivers/net/ethernet/netrono... (they really said "you get the gist" with that truncation 😭), dated October 2026, and it's all about struct nfp_bpf_reg_state(9). go forth and slay your BPF paths πŸ’–β­πŸ‘‘

πŸ“¦ where this page comes from