mlx5dr_send...te_send_info(9)

✨ NAME ✨

okay so bestie, this is page mlx5dr_send...te_send_info(9) from the Kernel API Manual 📖 — and the function it's serving is mlx5dr_send_fill_and_append_ste_send_info, whose whole job is: Add data to be sent with send_list parameters: 🫶 (yes that colon is part of it, we don't question the ancients)

🦋 SYNOPSIS 🦋

void mlx5dr_send_fill_and_append_ste_send_info (struct mlx5dr_ste *ste ,
u16 size , u16 offset , u8 *data , struct mlx5dr_ste_send_info *ste_info
, struct list_head *send_list , bool copy_data );

like literally that's the whole signature, no cap 💅

💅 ARGUMENTS 💅

• ste — the data that attached to this specific ste 🧚
• size — of data to write
• offset — of the data from start of the hw_ste entry
• data — data (iconic, unbothered, minimal 👑)
• ste_info — ste to be sent with send_list
• send_list — to append into it 📥
• copy_data — if true, it indicates that the data should be kept, because it's not backuped any where (like in re-hash) 🫣. if false, it lets the data to be updated after it was added to the list ✨

ngl the true vs false thing is the whole vibe check of this function — true means keep it safe, we have no other copy, false means eh, it'll get updated later anyway. choose wisely bestie 💀

🎀 SEE ALSO 🎀

• Kernel file ./drivers/net/ethernet/mellanox/mlx5/core/steering/sws/dr_send.c 📂
• mlx5dr_send_postsend_ste(9) 🌈

and that's the page, periodt 💖 this cutie comes to you from ./drivers/net/ethernet/mellano..., dated October 2026, and it's filed under the very same name we screamed at the top — mlx5dr_send...te_send_info(9) 🎀✨ bye bestie, go forth and append 🦋