Message ID | 20240911091333.1870071-1-vadfed@meta.com (mailing list archive) |
---|---|
Headers | show |
Series | Add option to provide OPT_ID value via cmsg | expand |
On Wed, 11 Sep 2024 02:13:30 -0700 Vadim Fedorenko wrote: > SOF_TIMESTAMPING_OPT_ID socket option flag gives a way to correlate TX > timestamps and packets sent via socket. Unfortunately, there is no way > to reliably predict socket timestamp ID value in case of error returned > by sendmsg. For UDP sockets it's impossible because of lockless > nature of UDP transmit, several threads may send packets in parallel. In > case of RAW sockets MSG_MORE option makes things complicated. More > details are in the conversation [1]. > This patch adds new control message type to give user-space > software an opportunity to control the mapping between packets and > values by providing ID with each sendmsg. Does not apply to net-next any more, sorry :(