From: Kuniyuki Iwashima <kuniyu@google.com>
To: Eric Dumazet <edumazet@kernel.org>,
Neal Cardwell <ncardwell@google.com>,
Matthieu Baerts <matttbe@kernel.org>,
Mat Martineau <martineau@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Geliang Tang <geliang@kernel.org>,
Simon Horman <horms@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
netdev@vger.kernel.org
Subject: [PATCH v2 net-next 1/2] tcp: Don't call tcp_update_recv_tstamps() if not needed.
Date: Thu, 5 Nov 2026 21:51:45 +0000 [thread overview]
Message-ID: <20261105215209.3160316-2-kuniyu@google.com> (raw)
In-Reply-To: <20261105215209.3160316-1-kuniyu@google.com>
When RX HWtstamp is enabled on NIC, skb_hwtstamps(skb)->hwtstamp
is set, which sets TCP_SKB_CB(skb)->has_rxtstamp to true.
In addition, TCP_SKB_CB(skb)->has_rxtstamp is also set from
skb->tstamp, which is set when one socket (e.g. tcpdump, PTP
daemon, etc) enables software RX timestamps (netstamp_needed_key).
Then, tcp_recvmsg_locked() always calls tcp_update_recv_tstamps()
and sets TCP_CMSG_TS to cmsg_flags so that later tcp_recvmsg()
calls tcp_recv_timestamp() after release_sock().
If a socket does not have SOCK_RCVTSTAMP in sk->sk_flags or any
flags set in sk->sk_tsflags, tcp_recv_timestamp() does nothing.
However, it is not free because sk->sk_tsflags shares the same
cacheline with sk->sk_forward_alloc, which is always modified
under lock_sock()/bh_lock_sock(), causing cacheline bouncing.
0.31 │ 403: test %al,%al
0.02 │ ↓ je 4a0
12.40 │ test $0x2,%bpl ; if (cmsg_flags & TCP_CMSG_TS)
│ ↓ je 48f
11.59 │ mov 0x60(%r14),%r15 ; sock_flag(sk, SOCK_TSTAMP_NEW)
12.25 │ mov 0x170(%r14),%ebx ; READ_ONCE(sk->sk_tsflags)
20.70 │ mov 0xd0(%rsp),%rdi ; if (tss->ts[0]) {
0.39 │ test %rdi,%rdi
│ ↓ je 44c
Also, sk->sk_flags is on the cold cacheline in tcp_recvmsg().
Commit f0e70409b7eb ("net: avoid unconditionally touching
sk_tsflags on RX") introduced SOCK_TIMESTAMPING_ANY to avoid
such false sharing.
Let's check SOCK_RCVTSTAMP and SOCK_TIMESTAMPING_ANY under
lock_sock().
We still need to touch sk->sk_flags, but with this change,
tcp_rr -T 128 -F 10000 gains ~3% more throughput on AMD EPYC
7B12 Zen 2 Rome (2 sockets, 256 vCPUs).
Signed-off-by: Kuniyuki Iwashima <kuniyu@google.com>
---
v2:
* Mention software tstamp
* s/sk_want_rx_tstamps/tcp_want_rx_tstamp_cmsg/ and
moved to include/net/tcp.h
* Use const in tcp_want_rx_tstamp()
---
include/net/tcp.h | 7 +++++++
net/ipv4/tcp.c | 13 ++++++++++---
2 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/include/net/tcp.h b/include/net/tcp.h
index 3560adddf821..f265ae06bb55 100644
--- a/include/net/tcp.h
+++ b/include/net/tcp.h
@@ -517,6 +517,13 @@ int tcp_set_rcvlowat(struct sock *sk, int val);
void tcp_set_rcvbuf(struct sock *sk, int val);
int tcp_set_window_clamp(struct sock *sk, int val);
+static inline bool tcp_want_rx_tstamp_cmsg(const struct sock *sk)
+{
+ return READ_ONCE(sk->sk_flags) &
+ ((1UL << SOCK_RCVTSTAMP) |
+ (1UL << SOCK_TIMESTAMPING_ANY));
+}
+
static inline void
tcp_update_recv_tstamps(struct sk_buff *skb,
struct scm_timestamping_internal *tss)
diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
index b9de7c302ba8..a1f89c1fa2ae 100644
--- a/net/ipv4/tcp.c
+++ b/net/ipv4/tcp.c
@@ -1878,6 +1878,13 @@ void tcp_set_rcvbuf(struct sock *sk, int val)
tcp_set_window_clamp(sk, tcp_win_from_space(sk, val));
}
+static bool tcp_want_rx_tstamp(const struct sock *sk,
+ const struct sk_buff *skb)
+{
+ return TCP_SKB_CB(skb)->has_rxtstamp &&
+ tcp_want_rx_tstamp_cmsg(sk);
+}
+
#ifdef CONFIG_MMU
static const struct vm_operations_struct tcp_vm_ops = {
};
@@ -2069,7 +2076,7 @@ static int tcp_zc_handle_leftover(struct tcp_zerocopy_receive *zc,
offset = *seq - TCP_SKB_CB(skb)->seq;
} else {
skb = tcp_recv_skb(sk, *seq, &offset);
- if (TCP_SKB_CB(skb)->has_rxtstamp) {
+ if (tcp_want_rx_tstamp(sk, skb)) {
tcp_update_recv_tstamps(skb, tss);
zc->msg_flags |= TCP_CMSG_TS;
}
@@ -2280,7 +2287,7 @@ static int tcp_zerocopy_receive(struct sock *sk,
if (!skb_frags_readable(skb))
break;
- if (TCP_SKB_CB(skb)->has_rxtstamp) {
+ if (tcp_want_rx_tstamp(sk, skb)) {
tcp_update_recv_tstamps(skb, tss);
zc->msg_flags |= TCP_CMSG_TS;
}
@@ -2893,7 +2900,7 @@ static int tcp_recvmsg_locked(struct sock *sk, struct msghdr *msg, size_t len,
tcp_fast_path_check(sk);
}
- if (TCP_SKB_CB(skb)->has_rxtstamp) {
+ if (tcp_want_rx_tstamp(sk, skb)) {
tcp_update_recv_tstamps(skb, tss);
*cmsg_flags |= TCP_CMSG_TS;
}
--
2.56.0.455.g6c5a503b38-goog
next prev parent reply other threads:[~2026-11-05 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 21:51 [PATCH v2 net-next 0/2] tcp/mptcp: Don't call tcp_update_recv_tstamps() if not needed Kuniyuki Iwashima
2026-11-05 21:51 ` Kuniyuki Iwashima [this message]
2026-11-05 21:51 ` [PATCH v2 net-next 2/2] mptcp: " Kuniyuki Iwashima
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=20261105215209.3160316-2-kuniyu@google.com \
--to=kuniyu@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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