libeth_xsktmo_req_csum(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– XSk Tx metadata op to request checksum offload πŸ’–

okay bestie, welcome to the libeth_xsktmo_req_csum(9) page from the Kernel API Manual β€” it’s giving β€œtiny helper, big checksum-offload energy” ✨


🌸 NAME 🌸

libeth_xsktmo_req_csum β€” XSk Tx metadata op to request checksum offload. That’s the whole name, and yes it ate πŸ’…


✨ SYNOPSIS ✨

void libeth_xsktmo_req_csum (u16 csum_start , u16 csum_offset , void *priv );

πŸŽ€ ARGUMENTS πŸŽ€

  • csum_start β€” unused. Not β€œused a little,” not β€œused sometimes.” Unused, bestie πŸ™ˆ
  • csum_offset β€” unused. Same vibe. Unused 🫢
  • priv β€” the libeth_xdp_tx_desc from the filling helper. That’s the one you pass in πŸ’–

πŸ’… DESCRIPTION πŸ’…

This is the generic implementation of ::tmo_request_checksum. Iconic, lowkey, does its one job ✨

⚠️ caveat time, bestie: it works only when HW doesn’t require filling checksum offsets and other parameters beside the checksum request bit. That’s the whole condition. No cap.

Consider using it within libeth_xsktmo unless the driver requires HW-specific callbacks. That’s the recommendation, fr fr πŸ¦‹


πŸ¦‹ SEE ALSO πŸ¦‹


mwah πŸ’‹ β€” source: ./include/net/libeth, version/date: October 2026, and this was libeth_xsktmo_req_csum(9) from the Kernel API Manual. bye bestie, go request that checksum 🫢

πŸ“¦ where this page comes from