[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172806963180.2712736.12630737288556684107.git-patchwork-notify@kernel.org>
Date: Fri, 04 Oct 2024 19:20:31 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vadim Fedorenko <vadfed@...a.com>
Cc: vadim.fedorenko@...ux.dev, willemb@...gle.com, kuba@...nel.org,
pabeni@...hat.com, dsahern@...nel.org, kerneljasonxing@...il.com,
horms@...nel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v6 0/3] Add option to provide OPT_ID value via cmsg
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 1 Oct 2024 05:57:13 -0700 you 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.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/3] net_tstamp: add SCM_TS_OPT_ID to provide OPT_ID in control message
https://git.kernel.org/netdev/net-next/c/4aecca4c7680
- [net-next,v6,2/3] net_tstamp: add SCM_TS_OPT_ID for RAW sockets
https://git.kernel.org/netdev/net-next/c/822b5bc6db55
- [net-next,v6,3/3] selftests: txtimestamp: add SCM_TS_OPT_ID test
https://git.kernel.org/netdev/net-next/c/a89568e9be75
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists