Message ID | 20241228184949.31582-9-yury.norov@gmail.com |
---|---|
State | New |
Headers | show |
Series | cpumask: cleanup cpumask_next_wrap() implementation and usage | expand |
On Sat, Dec 28, 2024 at 10:49:40AM -0800, Yury Norov wrote: > Calling cpumask_next_wrap_old() with starting CPU == -1 effectively means > the request to find next CPU, wrapping around if needed. > > cpumask_next_wrap() is the proper replacement for that. > > Signed-off-by: Yury Norov <yury.norov@gmail.com> Acked-by: Daniel Jordan <daniel.m.jordan@oracle.com>
diff --git a/kernel/padata.c b/kernel/padata.c index 454ff2fca40b..a886e5bf028c 100644 --- a/kernel/padata.c +++ b/kernel/padata.c @@ -274,7 +274,7 @@ static struct padata_priv *padata_find_next(struct parallel_data *pd, if (remove_object) { list_del_init(&padata->list); ++pd->processed; - pd->cpu = cpumask_next_wrap_old(cpu, pd->cpumask.pcpu, -1, false); + pd->cpu = cpumask_next_wrap(cpu, pd->cpumask.pcpu); } spin_unlock(&reorder->lock);
Calling cpumask_next_wrap_old() with starting CPU == -1 effectively means the request to find next CPU, wrapping around if needed. cpumask_next_wrap() is the proper replacement for that. Signed-off-by: Yury Norov <yury.norov@gmail.com> --- kernel/padata.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)