update_buffer_lossy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🫢 update_buffer_lossy(9) 🫢

okay so welcome to the Kernel API Manual, bestie β€” this page is literally all about update_buffer_lossy(9), and it's giving "tiny function, very specific job" energy ✨


🌸 NAME 🌸

update_buffer_lossy β€” Update buffer configuration based on pfc πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

int update_buffer_lossy (struct mlx5_core_dev *mdev , unsigned int
       max_mtu , u8 pfc_en , u8 *buffer , u32 xoff , u16 port_buff_cell_sz ,
       struct mlx5e_port_buffer *port_buffer , bool *change );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • mdev β€” port function core device πŸ‘‘
  • max_mtu β€” netdev's max_mtu
  • pfc_en β€” <input> current pfc configuration
  • buffer β€” <input> current prio to buffer mapping
  • xoff β€” <input> xoff value
  • port_buff_cell_sz β€” <input> port buffer cell_size
  • port_buffer β€” <output> port receive buffer configuration
  • change β€” <output>

πŸ’– DESCRIPTION πŸ’–

So this function updates the buffer configuration based on the pfc configuration and the priority to buffer mapping β€” no cap, that's the whole vibe 🫢

The buffer's lossy bit gets changed like this:

  • it goes lossless if there's at least one PFC enabled priority mapped to this buffer 🌈
  • it goes lossy if all priorities mapped to this buffer are PFC disabled πŸ’€

That's it. That's the lore. ✨


⭐ RETURN ⭐

Returns 0 if no error, and sets change to true if the buffer configuration was modified. periodt πŸ’…


🧚 SEE ALSO 🧚


and that's the page, bestie πŸŽ€ this cutie came from the Kernel API Manual, source/version ./drivers/net/ethernet/mellano..., dated October 2026, and yes β€” it's still update_buffer_lossy(9) at the end, iconic behavior only πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from