STRUCT NFP_PROG(9)

✨ struct nfp_prog(9) ✨

okay so this is the Kernel API Manual page for struct nfp_prog, which is, like, the nfp BPF program struct 💅 bestie, this is the whole vibe of a translated BPF program living its best life inside the nfp driver. grab a lil snack, we're going member by member 🍓

🌸 SYNOPSIS 🌸

struct nfp_prog {
    struct nfp_app_bpf *bpf;
    u64 *prog;
    unsigned int prog_len;
    unsigned int __prog_alloc_len;
    unsigned int stack_size;
    struct nfp_insn_meta *verifier_meta;
    enum bpf_prog_type type;
    unsigned int last_bpf_off;
    unsigned int tgt_out;
    unsigned int tgt_abort;
    unsigned int tgt_call_push_regs;
    unsigned int tgt_call_pop_regs;
    unsigned int n_translated;
    int error;
    unsigned int stack_frame_depth;
    unsigned int adjust_head_location;
    unsigned int map_records_cnt;
    unsigned int subprog_cnt;
    struct nfp_bpf_neutral_map **map_records;
    struct nfp_bpf_subprog_info *subprog;
    unsigned int n_insns;
    struct list_head insns;
 };

no cap, that's the whole struct, every single field, we do not skip 🫶

🎀 Members 🎀

okay this is the part where we meet the cast, main character energy only:

• bpf — backpointer to the bpf app priv structure. it's giving "knows where it came from" 💖
• prog — the machine code itself. the actual beef 🔥
• prog_len — number of valid instructions in the prog array. like, how many of them are actually real, bestie
• __prog_alloc_len — alloc size of the prog array. the mall budget vs. the actual spend, iykyk
• stack_size — total amount of stack used. the full stack situation 🌸
• verifier_meta — temporary storage for the verifier's insn meta. it's just visiting, it doesn't live here
• type — BPF program type. the genre of this program, if u will
• last_bpf_off — address of the last instruction translated from BPF. the lil landmark for where the translating got to
• tgt_out — jump target for normal exit. the happy path 🦋
• tgt_abort — jump target for abort (e.g. access outside of packet buffer). the "something went wrong" exit, dramatic but necessary 💀
• tgt_call_push_regs — jump target for subroutine for saving R6~R9 to stack. saving the registers, iconic behaviour
• tgt_call_pop_regs — jump target for subroutine used for restoring R6~R9. bringing them back, no cap
• n_translated — number of successfully translated instructions (for errors). the success counter, and yes it's also the error-reporting girlie
• error — error code if something went wrong. if this is set, we're not slaying, we're coping 😭
• stack_frame_depth — max stack depth for current frame. deep like my feelings about Unix tbh
• adjust_head_location — if program has single adjust head call — the insn no. one single call, one lil number, periodt
• map_records_cnt — the number of map pointers recorded for this prog
• subprog_cnt — number of sub-programs, including main function. yes, the main function counts, it's still a member of the family 💜
• map_records — the map record pointers from bpf->maps_neutral. neutral map records, very chill of them
• subprog — pointer to an array of objects holding info about sub-programs. a whole lil array of sub-program lore
• n_insns — number of instructions on insns list
• insns — list of BPF instruction wrappers (struct nfp_insn_meta)

🌈 SEE ALSO 🌈

go read these next, bestie, they're all in the kernel file ./drivers/net/ethernet/netronome/nfp/bpf/main.h:

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

✨ friendly reminder: this page is straight outta ./drivers/net/ethernet/netrono... (yes the header truncates it, that's just how it is) and it's dated October 2026 🌸

okay that's the whole page, you ate that, go forth and translate some BPF, mwah 💖🎀🫶