All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Srikar Dronamraju <srikar@linux.ibm.com>,
	 LKML <linux-kernel@vger.kernel.org>,
	 netdev@vger.kernel.org,  David S Miller <davem@davemloft.net>
Cc: Ingo Molnar <mingo@kernel.org>,
	 Peter Zijlstra <peterz@infradead.org>,
	 Dietmar Eggemann <dietmar.eggemann@arm.com>,
	 Dust Li <dust.li@linux.alibaba.com>,
	 D Wythe <alibuda@linux.alibaba.com>,
	 Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,  Jon Maloy <jmaloy@redhat.com>,
	 Kuniyuki Iwashima <kuniyu@google.com>,
	 linux-sctp@vger.kernel.org,
	 Mahanta Jambigi <mjambigi@linux.ibm.com>,
	 Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	 Paolo Abeni <pabeni@redhat.com>,
	 Sidraya Jayagond <sidraya@linux.ibm.com>,
	 Simon Horman <horms@kernel.org>,
	 Tony Lu <tonylu@linux.alibaba.com>,
	 Wen Gu <guwen@linux.alibaba.com>,
	 Wenjia Zhang <wenjia@linux.ibm.com>,
	 Willem de Bruijn <willemb@google.com>,
	 Xin Long <lucien.xin@gmail.com>,
	 Shrikanth Hegde <sshegde@linux.ibm.com>,
	 Vincent Guittot <vincent.guittot@linaro.org>,
	 Steven Rostedt <rostedt@goodmis.org>,
	 Ben Segall <bsegall@google.com>,  Mel Gorman <mgorman@suse.de>,
	 Valentin Schneider <vschneid@redhat.com>,
	 K Prateek Nayak <kprateek.nayak@amd.com>,
	 Srikar Dronamraju <srikar@linux.ibm.com>
Subject: Re: [PATCH 1/2] net/socket: Record preference for synchronous wakeups
Date: Tue, 21 Jul 2026 04:00:59 -0400	[thread overview]
Message-ID: <willemdebruijn.kernel.53771955fa7f@gmail.com> (raw)
In-Reply-To: <20260714013940.4068189-5-srikar@linux.ibm.com>

Srikar Dronamraju wrote:
> Scheduler differentiates between affine and non-affine wakeups by the
> way of sync flags. Scheduler prefers to pull the tasks towards the waker
> if the sync flag is set.
> 
> In some cases, socket APIs are blindly requesting sync wakeups. This may
> cause load-balance issues and non-optimal performance.
> 
> Record whether the most recent blocking socket operation could benefit

What is the heuristic that determines this?

If respinning, please state that explicitly in the commit message.


> from synchronous wakeups. Subsequent readiness notifications use this
> hint to determine whether WF_SYNC should be propagated.
> 
> The flag is advisory and affects only wakeup placement decisions.
> 
> Signed-off-by: Srikar Dronamraju <srikar@linux.ibm.com>

  parent reply	other threads:[~2026-07-21  8:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  1:39 [PATCH 0/2] net: Use synchronous wakeups selectively Srikar Dronamraju
2026-07-14  1:39 ` [PATCH 1/2] net/socket: Record preference for synchronous wakeups Srikar Dronamraju
2026-07-21  5:00   ` Shrikanth Hegde
2026-07-21  8:00   ` Willem de Bruijn [this message]
2026-07-14  1:39 ` [PATCH 2/2] net/sock: Propagate WF_SYNC only when requested Srikar Dronamraju
2026-07-21  4:50   ` Shrikanth Hegde
2026-07-22 17:08 ` [PATCH 0/2] net: Use synchronous wakeups selectively Jakub Kicinski

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.53771955fa7f@gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=bsegall@google.com \
    --cc=davem@davemloft.net \
    --cc=dietmar.eggemann@arm.com \
    --cc=dust.li@linux.alibaba.com \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=mjambigi@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sidraya@linux.ibm.com \
    --cc=srikar@linux.ibm.com \
    --cc=sshegde@linux.ibm.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=wenjia@linux.ibm.com \
    --cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.