[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231108101552.7ebbb52d@gandalf.local.home>
Date: Wed, 8 Nov 2023 10:15:52 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: David Laight <David.Laight@...LAB.COM>
Cc: 'Ankur Arora' <ankur.a.arora@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"peterz@...radead.org" <peterz@...radead.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"paulmck@...nel.org" <paulmck@...nel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"x86@...nel.org" <x86@...nel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"luto@...nel.org" <luto@...nel.org>, "bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"hpa@...or.com" <hpa@...or.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"juri.lelli@...hat.com" <juri.lelli@...hat.com>,
"vincent.guittot@...aro.org" <vincent.guittot@...aro.org>,
"willy@...radead.org" <willy@...radead.org>,
"mgorman@...e.de" <mgorman@...e.de>,
"jon.grimm@....com" <jon.grimm@....com>,
"bharata@....com" <bharata@....com>,
"raghavendra.kt@....com" <raghavendra.kt@....com>,
"boris.ostrovsky@...cle.com" <boris.ostrovsky@...cle.com>,
"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
"jgross@...e.com" <jgross@...e.com>,
"andrew.cooper3@...rix.com" <andrew.cooper3@...rix.com>,
"mingo@...nel.org" <mingo@...nel.org>,
"bristot@...nel.org" <bristot@...nel.org>,
"mathieu.desnoyers@...icios.com" <mathieu.desnoyers@...icios.com>,
"geert@...ux-m68k.org" <geert@...ux-m68k.org>,
"glaubitz@...sik.fu-berlin.de" <glaubitz@...sik.fu-berlin.de>,
"anton.ivanov@...bridgegreys.com" <anton.ivanov@...bridgegreys.com>,
"mattst88@...il.com" <mattst88@...il.com>,
"krypton@...ich-teichert.org" <krypton@...ich-teichert.org>,
"richard@....at" <richard@....at>,
"mjguzik@...il.com" <mjguzik@...il.com>
Subject: Re: [RFC PATCH 00/86] Make the kernel preemptible
On Wed, 8 Nov 2023 09:43:10 +0000
David Laight <David.Laight@...LAB.COM> wrote:
> > Policies:
> >
> > A - preemption=none: run to completion
> > B - preemption=voluntary: run to completion, unless a task of higher
> > sched-class awaits
> > C - preemption=full: optimized for low-latency. Preempt whenever a higher
> > priority task awaits.
>
> If you remove cond_resched() then won't both B and C require an extra IPI.
> That is probably OK for RT tasks but could get expensive for
> normal tasks that aren't bound to a specific cpu.
What IPI is extra?
>
> I suspect C could also lead to tasks being pre-empted just before
> they sleep (eg after waking another task).
> There might already be mitigation for that, I'm not sure if
> a voluntary sleep can be done in a non-pre-emptible section.
No, voluntary sleep can not be done in a preemptible section.
-- Steve
Powered by blists - more mailing lists