[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4cb1a9ae15c414435020630cf6362163ddda1550.camel@gmx.de>
Date: Wed, 17 Mar 2021 05:43:27 +0100
From: Mike Galbraith <efault@....de>
To: Wang Qing <wangqing@...o.com>, Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched: swait: use wake_up_process() instead of
wake_up_state()
On Tue, 2021-03-16 at 19:20 +0800, Wang Qing wrote:
> Why not just use wake_up_process().
IMO this is not an improvement. There are other places where explicit
TASK_NORMAL is used as well, and they're all perfectly clear as is.
> Signed-off-by: Wang Qing <wangqing@...o.com>
> ---
> kernel/sched/swait.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/swait.c b/kernel/sched/swait.c
> index e1c655f..7a24925
> --- a/kernel/sched/swait.c
> +++ b/kernel/sched/swait.c
> @@ -69,7 +69,7 @@ void swake_up_all(struct swait_queue_head *q)
> while (!list_empty(&tmp)) {
> curr = list_first_entry(&tmp, typeof(*curr), task_list);
>
> - wake_up_state(curr->task, TASK_NORMAL);
> + wake_up_process(curr->task);
> list_del_init(&curr->task_list);
>
> if (list_empty(&tmp))
Powered by blists - more mailing lists