On Wed, Jul 08, 2026 at 06:32:02PM +0200, Eric Dumazet wrote:

On Wed, Jul 8, 2026 at 6:09 PM Usama Arif [off-list ref] wrote:

quoted

So the workload has SO_TIMESTAMPING enabled on its TCP sockets, and every
packet completion and every ACK triggers a timestamp delivery through the
error-queue path, which is why sock_def_error_report fires.

It seems we can not please everyone.

https://lore.kernel.org/netdev/20260526063650.952-1-xuewen.yan@unisoc.com/ (local)

Perhaps this SYNC heuristic should be a per-socket choice so that
applications can decide what is best for them.

Instead of adding a new socket option, perhaps use SO_TIMESTAMPING to
decide whether to use sync or not?  There could be other socket options
which also report a high rate of "errors", but until those show up I
think just testing on this one socket option should be fine.