From: Xuewen Yan <xuewen.yan@unisoc.com>
To: <edumazet@google.com>, <kuniyu@google.com>, <pabeni@redhat.com>,
<willemb@google.com>, <davem@davemloft.net>, <kuba@kernel.org>,
<horms@kernel.org>
Cc: <peterz@infradead.org>, <mingo@redhat.com>,
<vincent.guittot@linaro.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <ke.wang@unisoc.com>,
<guohua.yan@unisoc.com>, <Wade.Shu@unisoc.com>,
<xuewen.yan94@gmail.com>, <di.shen@unisoc.com>
Subject: [RFC PATCH] net/core: use wake_up_interruptible_poll() in sock_def_readable()
Date: Tue, 26 May 2026 14:36:50 +0800 [thread overview]
Message-ID: <20260526063650.952-1-xuewen.yan@unisoc.com> (raw)
sock_def_readable() currently uses wake_up_interruptible_sync_poll() to
wake up tasks waiting for readable data on a socket. The _sync variant
sets the WF_SYNC flag, which tells the scheduler that the waker will
schedule away soon, so the wakee should stay on the same CPU to avoid
needless cache bouncing.
However, we found that the following stack:
-vfs_write
-sock_write_iter
-unix_stream_sendmsg
-sock_def_readable
-__wake_up_sync_key
In this process-context scenario, the waker does NOT go to sleep
after the wakeup. With WF_SYNC, the scheduler is misled into placing
the wakee on the waker's CPU (via wake_affine_idle()'s sync path when
nr_running == 1), causing both the sender and receiver to contend for
the same CPU. This may hurt throughput for IPC workloads on multi-core
systems where the sender and receiver could otherwise run in parallel
on different CPUs.
Switch to wake_up_interruptible_poll() which does not set WF_SYNC.
This allows the scheduler to freely migrate the wakee to an idle CPU,
enabling true parallelism between the sending and receiving processes.
Co-developed-by: Guohua Yan <guohua.yan@unisoc.com>
Signed-off-by: Guohua Yan <guohua.yan@unisoc.com>
Signed-off-by: Xuewen Yan <xuewen.yan@unisoc.com>
---
Note:
The possible cost is that for softirq callers (TCP/UDP receive path), the wakee
may be migrated away from the current CPU where the received data is
cache-hot. However, this is mitigated by:
- The scheduler's existing wake_affine logic which already considers
cache affinity regardless of WF_SYNC.
We are not very familiar with the networking code here,
so we would greatly appreciate any suggestions or advice from the community.
Thanks!
---
net/core/sock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/core/sock.c b/net/core/sock.c
index b37b664b6eb9..42ab9373194f 100644
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -3611,7 +3611,7 @@ void sock_def_readable(struct sock *sk)
rcu_read_lock();
wq = rcu_dereference(sk->sk_wq);
if (skwq_has_sleeper(wq))
- wake_up_interruptible_sync_poll(&wq->wait, EPOLLIN | EPOLLPRI |
+ wake_up_interruptible_poll(&wq->wait, EPOLLIN | EPOLLPRI |
EPOLLRDNORM | EPOLLRDBAND);
sk_wake_async_rcu(sk, SOCK_WAKE_WAITD, POLL_IN);
rcu_read_unlock();
--
2.25.1
next reply other threads:[~2026-05-26 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 6:36 Xuewen Yan [this message]
2026-05-26 9:07 ` Jiayuan Chen
2026-05-26 11:06 ` Xuewen Yan
2026-06-04 7:20 ` Xuewen Yan
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=20260526063650.952-1-xuewen.yan@unisoc.com \
--to=xuewen.yan@unisoc.com \
--cc=Wade.Shu@unisoc.com \
--cc=davem@davemloft.net \
--cc=di.shen@unisoc.com \
--cc=edumazet@google.com \
--cc=guohua.yan@unisoc.com \
--cc=horms@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=willemb@google.com \
--cc=xuewen.yan94@gmail.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
all inboxes | Powered by JetHome®