STRUCT NFP_FL_CT_MAP_ENTRY(9)
π struct nfp_fl_ct_map_entry(9) π
okay bestie, so this is a page straight out of the Kernel API Manual and it's about one very specific little struct. it's not the main character of the conntrack story, but the whole plot falls apart without it, iykyk πΈ
β¨ NAME β¨
struct nfp_fl_ct_map_entry β the lil map between a flow cookie and a specific ct_flow, no cap π
π¦ SYNOPSIS π¦
struct nfp_fl_ct_map_entry {
unsigned long cookie;
struct rhash_head hash_node;
struct nfp_fl_ct_flow_entry *ct_entry;
};
that's the whole vibe. three fields, zero drama π
π Members π
cookieβ the flow cookie, same as the original TC flow, and it's used as the key. literally the ID badge for the lookup πhash_nodeβ used by the hashtable. it's the struct's little handshake with the hash table so it can get found again π§ct_entryβ pointer to the correspondingct_entry. it's giving "here's your actual conntrack entry, bestie" π
π SEE ALSO π
the kernel file is right here:
./drivers/net/ethernet/netronome/nfp/flower/conntrack.h
and the whole friend group, all of them, don't skip a single one:
struct nfp_fl_ct_zone_entry(9)struct nfp_fl_ct_flow_entry(9)struct nfp_fl_ct_tc_merge(9)struct nfp_fl_nft_tc_merge(9)nfp_fl_ct_handle_pre_ct(9)nfp_fl_ct_handle_post_ct(9)nfp_fl_create_new_pre_ct(9)nfp_fl_ct_clean_flow_entry(9)nfp_fl_ct_del_flow(9)nfp_fl_ct_handle_nft_flow(9)nfp_fl_ct_stats(9)
fr fr, go read the ones above if you wanna actually understand the conntrack pipeline β this struct is just the map, the rest is the journey π«Ά
and that's the page, mwah π β big kiss goodbye from ./drivers/net/ethernet/netrono..., dated October 2026, serving you struct nfp_fl_ct_map_entry(9) one last time βπ₯
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms