public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Use the NUMA scheduling domain for NUMA optimizations
Date: Wed, 4 Dec 2024 09:50:31 -1000	[thread overview]
Message-ID: <Z1CyhyYN_MBSro07@slm.duckdns.org> (raw)
In-Reply-To: <20241120142903.59521-1-arighi@nvidia.com>

On Wed, Nov 20, 2024 at 03:29:03PM +0100, Andrea Righi wrote:
> Rely on the NUMA scheduling domain topology, instead of accessing NUMA
> topology information directly.
> 
> There is basically no functional change, but in this way we ensure
> consistent use of the same topology information determined by the
> scheduling subsystem.
> 
> Fixes: f6ce6b949304 ("sched_ext: Do not enable LLC/NUMA optimizations when domains overlap")
> Signed-off-by: Andrea Righi <arighi@nvidia.com>

Applied to sched_ext/for-6.14.

Thanks.

-- 
tejun

      reply	other threads:[~2024-12-04 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 14:29 [PATCH] sched_ext: Use the NUMA scheduling domain for NUMA optimizations Andrea Righi
2024-12-04 19:50 ` Tejun Heo [this message]

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=Z1CyhyYN_MBSro07@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=arighi@nvidia.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