ixgbe_ipsec_vf_del_sa(9)
π ixgbe_ipsec_vf_del_sa β bestie edition
okay so real talk, this is ixgbe_ipsec_vf_del_sa from the Kernel API Manual, and it's lowkey the little cleanup crew of the ixgbe IPsec world. Let's get into it π«Ά
β¨ NAME β¨
ixgbe_ipsec_vf_del_sa β translate VF request to SA delete. that's it, that's the whole vibe: a VF asks for a delete, and this function is the translator that makes it happen π
π¦ SYNOPSIS π¦
int ixgbe_ipsec_vf_del_sa (struct ixgbe_adapter *adapter , u32 *msgbuf ,
u32 vf );
π ARGUMENTS π
adapterβ board private structure. the main character struct, obviously πmsgbufβ The message buffer. yes bestie, The message buffer, capital T πΈvfβ the VF index. which VF are we talking about? this one π
π DESCRIPTION π
so the VF slides in with its offload_handle, right? and we're like okay bestie let's find your related SA table entry, and once we've got it we take that entry's xs field and use it to call for a delete of the SA. slay. no cap, that's literally the whole thing β¨
π NOTE π
not me having to explain this one, but here goes β we silently ignore requests to delete entries that are already set to unused. why? because when a VF gets set to "DOWN", the PF first gets a reset and clears all the VF's entries, and then the VF's XFRM stack sends individual deletes for each entry that the reset already removed π« like, girl, they're already gone.
in the future it might be good to try to optimize this so not so many unnecessary delete messages are sent π₯ (future-you's problem, honestly)
Returns 0 or error value π
π§ gentle reminder: every one of those details matters β the "DOWN" state, the PF reset happening first, the XFRM stack sending individual deletes, and the fact that the reset already removed them. don't come for me, I'm just the messenger.
β SEE ALSO β
Kernel file ./drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c
and the whole friend group π«Ά:
ixgbe_ipsec_set_tx_sa(9)ixgbe_ipsec_set_rx_item(9)ixgbe_ipsec_set_rx_sa(9)ixgbe_ipsec_set_rx_ip(9)ixgbe_ipsec_clear_hw_tables(9)ixgbe_ipsec_stop_data(9)ixgbe_ipsec_stop_engine(9)ixgbe_ipsec_start_engine(9)ixgbe_ipsec_restore(9)ixgbe_ipsec_find_empty_idx(9)ixgbe_ipsec_find_rx_state(9)ixgbe_ipsec_parse_proto_keys(9)ixgbe_ipsec_check_mgmt_ip(9)ixgbe_ipsec_add_sa(9)ixgbe_ipsec_del_sa(9)ixgbe_ipsec_vf_clear(9)ixgbe_ipsec_vf_add_sa(9)ixgbe_ipsec_tx(9)ixgbe_ipsec_rx(9)ixgbe_init_ipsec_offload(9)ixgbe_stop_ipsec_offload(9)
and that's the tea π this page came from ./drivers/net/ethernet/intel/i..., dated October 2026, and it's called ixgbe_ipsec_vf_del_sa(9) β kbye, ily, go delete some SAs responsibly πβ¨π
π¦ 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