[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21925b706eb55d78afe40ae3e8d5778875821009.camel@linux.intel.com>
Date: Fri, 16 Dec 2022 08:58:55 -0800
From: srinivas pandruvada <srinivas.pandruvada@...ux.intel.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: rafael@...nel.org, frederic@...nel.org, daniel.lezcano@...aro.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
len.brown@...el.com
Subject: Re: [RFC/RFT PATCH 1/2] sched/core: Check and schedule ksoftirq
On Fri, 2022-12-16 at 12:19 +0100, Peter Zijlstra wrote:
> On Thu, Dec 15, 2022 at 10:42:59AM -0800, Srinivas Pandruvada wrote:
> > + /* Give ksoftirqd 1 jiffy to get a chance to start
> > its job */
> > + if (!READ_ONCE(it.done) &&
> > task_is_running(__this_cpu_read(ksoftirqd))) {
> > + __set_current_state(TASK_UNINTERRUPTIBLE);
> > + schedule_timeout(1);
> > + }
>
> That's absolutely disgusting :-/
What is the alternative? Process softirq in this task context for one
time?
Thanks,
Srinivas
Powered by blists - more mailing lists