public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: David Carlier <devnexen@gmail.com>, David Vernet <void@manifault.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: add unlikely() hints in do_enqueue_task() hot path
Date: Thu, 26 Feb 2026 12:08:41 -1000	[thread overview]
Message-ID: <910584a388b5647dbccc2807bc2aa234@kernel.org> (raw)
In-Reply-To: <20260226175019.40449-1-devnexen@gmail.com>

Hello,

It looks like the patch accidentally includes a CLAUDE.md file creation.
Could you drop that and resend?

Also, for the PF_EXITING and migration_disabled checks, the original code
intentionally places unlikely() only on the runtime condition (e.g.
p->flags & PF_EXITING). Moving it to wrap the entire condition loses that
precision. It'd be better to keep those as they are and only add
unlikely() to the scx_rq_online() and scx_rq_bypassing() checks.

Thanks.

--
tejun

  reply	other threads:[~2026-02-26 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 17:50 [PATCH] sched_ext: add unlikely() hints in do_enqueue_task() hot path David Carlier
2026-02-26 22:08 ` Tejun Heo [this message]
2026-02-27 17:40   ` David CARLIER
  -- strict thread matches above, loose matches on Subject: below --
2026-02-26 22:44 David Carlier
2026-02-27 17:30 ` Tejun Heo

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=910584a388b5647dbccc2807bc2aa234@kernel.org \
    --to=tj@kernel.org \
    --cc=devnexen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=void@manifault.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