[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1f94c48b4e0e7d73a689a076f78f0892095b4d89.camel@surriel.com>
Date: Mon, 09 May 2022 15:49:52 -0400
From: Rik van Riel <riel@...riel.com>
To: Josh Poimboeuf <jpoimboe@...nel.org>
Cc: Song Liu <song@...nel.org>, linux-kernel@...r.kernel.org,
live-patching@...r.kernel.org, mingo@...hat.com,
peterz@...radead.org, vincent.guittot@...aro.org,
jpoimboe@...hat.com, joe.lawrence@...hat.com, kernel-team@...com
Subject: Re: [RFC] sched,livepatch: call stop_one_cpu in
klp_check_and_switch_task
On Mon, 2022-05-09 at 12:17 -0700, Josh Poimboeuf wrote:
> On Mon, May 09, 2022 at 03:10:16PM -0400, Rik van Riel wrote:
>
>
> > Should kernel threads that can use a lot of CPU have
> > something in their outer loop to transition KLPs,
> > just like the idle task does?
>
> Maybe - I suppose this is the first time we've had an issue with
> CPU-bound kthreads. I didn't know that was a thing ;-)
>
Kworkers have as much work as you want them to do, and with
things like btrfs compression that can be quite a bit.
--
All Rights Reversed.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists