mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valentin Schneider <vschneid@redhat.com>
To: Huang Ying <ying.huang@intel.com>, Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Huang Ying <ying.huang@intel.com>,
	Valentin Schneider <valentin.schneider@arm.com>,
	Ingo Molnar <mingo@redhat.com>, Mel Gorman <mgorman@suse.de>,
	Rik van Riel <riel@surriel.com>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Subject: Re: [PATCH] sched,topology: Update sched topology atomically
Date: Mon, 11 Apr 2022 09:22:13 +0100	[thread overview]
Message-ID: <xhsmh7d7wni6i.mognet@vschneid.remote.csb> (raw)
In-Reply-To: <xhsmhczhrwm9z.mognet@vschneid.remote.csb>

On 08/04/22 17:52, Valentin Schneider wrote:
>> +	topology = rcu_dereference(sched_numa_topology);
>> +	for (i = 0; i < topology->nr_levels; i++) {
>> +		if (!topology->masks[i][j])
>
> If I got default_numa_topology right and it's meant to be static,
> sched_numa_topology->masks can still be NULL, but here this would be gated
> by nr_levels being 0... Did I get that right?
>

Being a file-global variable, that's already init'd-as-0, (I'll use
my longish break as an excuse for forgetting that one), but the rest still
applies.

>>                       break;
>> -		cpu = cpumask_any_and(cpus, masks[i][j]);
>> +		cpu = cpumask_any_and(cpus, topology->masks[i][j]);
>>               if (cpu < nr_cpu_ids) {
>>                       found = cpu;
>>                       break;
>>               }
>>       }
>> -unlock:
>>       rcu_read_unlock();
>>
>>       return found;
>> --
>> 2.30.2


  reply	other threads:[~2022-04-11  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  7:01 Huang Ying
2022-04-08 16:52 ` Valentin Schneider
2022-04-11  8:22   ` Valentin Schneider [this message]
2022-04-11  9:01   ` ying.huang

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=xhsmh7d7wni6i.mognet@vschneid.remote.csb \
    --to=vschneid@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=valentin.schneider@arm.com \
    --cc=ying.huang@intel.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®