From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Tejun Heo <tj@kernel.org>, Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [PATCH v6 3/5] sched: Enforce user requested affinity
Date: Wed, 31 Aug 2022 17:00:16 -0400 [thread overview]
Message-ID: <4ac0cfd5-cf1e-9bcd-7476-494bfbeb1c50@redhat.com> (raw)
In-Reply-To: <Yw8n/Ef1NWnwmHYW@hirez.programming.kicks-ass.net>
On 8/31/22 05:21, Peter Zijlstra wrote:
> On Wed, Aug 31, 2022 at 11:18:22AM +0200, Peter Zijlstra wrote:
>> On Thu, Aug 25, 2022 at 09:01:17PM -0400, Waiman Long wrote:
>>
>>> @@ -9352,6 +9381,11 @@ int sched_cpu_activate(unsigned int cpu)
>>> sched_update_numa(cpu, true);
>>> sched_domains_numa_masks_set(cpu);
>>> cpuset_cpu_active();
>>> + /*
>>> + * Preallocated scratch cpumask
>>> + */
>>> + if (!rq->scratch_mask)
>>> + rq->scratch_mask = kmalloc(cpumask_size(), GFP_KERNEL);
>>> }
>> this is too late; I think you'll have to add a sched_cpu_prepare() and
>> simply fail the cpu-up when the allocation fails.
> Alternatively, waste some more memory and add yet another per-cpu
> cpumask.
A percpu cpumask is probably a better idea. However, I don't need that
as early as the other cpumasks like __cpu_possible_mask. Maybe I can do
a percpu memory allocation early in the pre-smp boot.
Cheers,
Longman
next prev parent reply other threads:[~2022-08-31 21:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 1:01 [PATCH v6 0/5] sched: Persistent " Waiman Long
2022-08-26 1:01 ` [PATCH v6 1/5] sched: Add __releases annotations to affine_move_task() Waiman Long
2022-08-26 1:01 ` [PATCH v6 2/5] sched: Use user_cpus_ptr for saving user provided cpumask in sched_setaffinity() Waiman Long
2022-08-31 9:12 ` Peter Zijlstra
2022-08-31 20:46 ` Waiman Long
2022-08-26 1:01 ` [PATCH v6 3/5] sched: Enforce user requested affinity Waiman Long
2022-08-31 9:14 ` Peter Zijlstra
2022-08-31 9:18 ` Peter Zijlstra
2022-08-31 9:21 ` Peter Zijlstra
2022-08-31 21:00 ` Waiman Long [this message]
2022-08-31 20:48 ` Waiman Long
2022-08-26 1:01 ` [PATCH v6 4/5] sched: Handle set_cpus_allowed_ptr() & sched_setaffinity() race Waiman Long
2022-08-31 9:26 ` Peter Zijlstra
2022-08-31 20:53 ` Waiman Long
2022-08-31 9:47 ` Peter Zijlstra
2022-08-31 20:56 ` Waiman Long
2022-08-26 1:01 ` [PATCH v6 5/5] sched: Fix sched_setaffinity() and fork/clone() race Waiman Long
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=4ac0cfd5-cf1e-9bcd-7476-494bfbeb1c50@redhat.com \
--to=longman@redhat.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=jiangshanlai@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@kernel.org \
/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®