update_buffer_lossy(9)
π«Ά 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_mtupfc_enβ<input>current pfc configurationbufferβ<input>current prio to buffer mappingxoffβ<input>xoff valueport_buff_cell_szβ<input>port buffer cell_sizeport_bufferβ<output>port receive buffer configurationchangeβ<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 π§
- Kernel file
./drivers/net/ethernet/mellanox/mlx5/core/en/port_buffer.c select_sbcm_params(9)
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
- 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