From: Willem de Bruijn <willemdebruijn.kernel@gmail•com>
To: Jason Xing <kerneljasonxing@gmail•com>,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, horms@kernel•org, willemb@google•com,
martin.lau@kernel•org
Cc: netdev@vger•kernel.org, bpf@vger•kernel.org,
Jason Xing <kernelxing@tencent•com>,
Yushan Zhou <katrinzhou@tencent•com>
Subject: Re: [PATCH net-next v2 2/4] tcp: advance the tsflags check to save cycles
Date: Sun, 05 Apr 2026 22:23:27 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.c2ef8ef43869@gmail.com> (raw)
In-Reply-To: <20260404150452.83904-3-kerneljasonxing@gmail.com>
Jason Xing wrote:
> From: Jason Xing <kernelxing@tencent•com>
>
> Check the tsflags first to see if the socket timestamping is enabled.
> If so, then try to fetch the last skb from either write queue or
> retransmission queue.
This message does not explain why this change is made.
next prev parent reply other threads:[~2026-04-06 2:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 15:04 [PATCH net-next v2 0/4] bpf-timestamp: convert to push-level granularity Jason Xing
2026-04-04 15:04 ` [PATCH net-next v2 1/4] tcp: separate BPF timestamping from tcp_tx_timestamp Jason Xing
2026-04-04 15:04 ` [PATCH net-next v2 2/4] tcp: advance the tsflags check to save cycles Jason Xing
2026-04-06 2:23 ` Willem de Bruijn [this message]
2026-04-06 11:48 ` Jason Xing
2026-04-04 15:04 ` [PATCH net-next v2 3/4] bpf-timestamp: keep track of the skb when wait_for_space occurs Jason Xing
2026-04-06 2:28 ` Willem de Bruijn
2026-04-06 11:59 ` Jason Xing
2026-04-06 14:37 ` Willem de Bruijn
2026-04-07 3:33 ` Jason Xing
2026-04-07 7:43 ` Jason Xing
2026-04-07 21:17 ` Willem de Bruijn
2026-04-08 0:35 ` Jason Xing
2026-04-08 7:30 ` Jason Xing
2026-04-08 15:15 ` Willem de Bruijn
2026-04-08 18:12 ` Martin KaFai Lau
2026-04-08 23:52 ` Jason Xing
2026-04-08 23:05 ` Jason Xing
2026-04-04 15:04 ` [PATCH net-next v2 4/4] bpf-timestamp: complete tracing the skb from each push in sendmsg Jason Xing
2026-04-06 2:17 ` [PATCH net-next v2 0/4] bpf-timestamp: convert to push-level granularity Willem de Bruijn
2026-04-06 12:25 ` Jason Xing
2026-04-06 14:38 ` Willem de Bruijn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=willemdebruijn.kernel.c2ef8ef43869@gmail.com \
--to=willemdebruijn.kernel@gmail$(echo .)com \
--cc=bpf@vger$(echo .)kernel.org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=katrinzhou@tencent$(echo .)com \
--cc=kerneljasonxing@gmail$(echo .)com \
--cc=kernelxing@tencent$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=martin.lau@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=willemb@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox