From: "Paul E. McKenney" <paulmck@kernel.org> To: Thomas Gleixner <tglx@linutronix.de> Cc: peterz@infradead.org, Valentin Schneider <valentin.schneider@arm.com>, Vladimir Oltean <olteanv@gmail.com>, Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>, Alison Wang <alison.wang@nxp.com>, catalin.marinas@arm.com, will@kernel.org, mw@semihalf.com, leoyang.li@nxp.com, vladimir.oltean@nxp.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Anna-Maria Gleixner <anna-maria@linutronix.de> Subject: Re: [RFC PATCH] arm64: defconfig: Disable fine-grained task level IRQ time accounting Date: Thu, 6 Aug 2020 13:39:14 -0700 [thread overview] Message-ID: <20200806203914.GQ4295@paulmck-ThinkPad-P72> (raw) In-Reply-To: <87k0ybha0z.fsf@nanos.tec.linutronix.de> On Thu, Aug 06, 2020 at 09:03:24PM +0200, Thomas Gleixner wrote: > Paul, > > "Paul E. McKenney" <paulmck@kernel.org> writes: > > On Thu, Aug 06, 2020 at 01:45:45PM +0200, peterz@infradead.org wrote: > >> The safety thing is concerned with RT tasks. It doesn't pretend to help > >> with runnaway IRQs, never has, never will. > > > > Getting into the time machine back to the 1990s... > > > > DYNIX/ptx had a discretionary mechanism to deal with excessive interrupts. > > There was a function that long-running interrupt handlers were supposed > > to call periodically that would return false if the system felt that > > the CPU had done enough interrupts for the time being. In that case, > > the interrupt handler was supposed to schedule itself for a later time, > > but leave the interrupt unacknowledged in order to prevent retriggering > > in the meantime. > > > > Of course, this mechanism would be rather less helpful in Linux. > > > > For one, Linux has way more device drivers and way more oddball devices. > > In contrast, the few devices that DYNIX/ptx supported were carefully > > selected, and the selection criteria included being able to put up > > with this sort of thing. Also, the fact that there was but a handful > > of device drivers meant that changes like this could be more easily > > propagated through all drivers. > > We could do that completely at the core interrupt handling level. Ah, true enough if the various NAPI-like devices give up the CPU from time to time. Which they might well do for all I know. > > Also, Linux supports way more workloads. In contrast, DYNIX/ptx could > > pick a small percentage of each CPU that would be permitted to be used > > by hardware interrupt handlers. As in there are probably Linux workloads > > that run >90% of some poor CPU within hardware interrupt handlers. > > Yet another tunable. /me runs ;-) ;-) ;-) If there are workloads that would like to be able to keep one or more CPUs completely busy handling interrupts, it should be possible to create something that is used sort of like cond_resched() to keep RCU, the scheduler, and the various watchdogs and lockup detectors at bay. For example, RCU could supply a function that checked to make sure that it was in an interrupt from idle, and if so report a quiescent state for that CPU. So if the CPU was idle and there wasn't anything pending for it, that CPU could safely stay in a hardirq handler indefinitely. I suppose that the function should return an indication in cases such as interrupt from non-idle. Sort of like NO_HZ_FULL, but for hardirq handlers, and also allowing those handlers to use RCU read-side critical sections. Or we could do what all the cool kids do these days, namely just apply machine learning, thus automatically self-tuning in real time. /me runs... Thanx, Paul
WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@kernel.org> To: Thomas Gleixner <tglx@linutronix.de> Cc: mw@semihalf.com, Anna-Maria Gleixner <anna-maria@linutronix.de>, peterz@infradead.org, catalin.marinas@arm.com, Alison Wang <alison.wang@nxp.com>, linux-kernel@vger.kernel.org, leoyang.li@nxp.com, vladimir.oltean@nxp.com, Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>, Vladimir Oltean <olteanv@gmail.com>, will@kernel.org, Valentin Schneider <valentin.schneider@arm.com>, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC PATCH] arm64: defconfig: Disable fine-grained task level IRQ time accounting Date: Thu, 6 Aug 2020 13:39:14 -0700 [thread overview] Message-ID: <20200806203914.GQ4295@paulmck-ThinkPad-P72> (raw) In-Reply-To: <87k0ybha0z.fsf@nanos.tec.linutronix.de> On Thu, Aug 06, 2020 at 09:03:24PM +0200, Thomas Gleixner wrote: > Paul, > > "Paul E. McKenney" <paulmck@kernel.org> writes: > > On Thu, Aug 06, 2020 at 01:45:45PM +0200, peterz@infradead.org wrote: > >> The safety thing is concerned with RT tasks. It doesn't pretend to help > >> with runnaway IRQs, never has, never will. > > > > Getting into the time machine back to the 1990s... > > > > DYNIX/ptx had a discretionary mechanism to deal with excessive interrupts. > > There was a function that long-running interrupt handlers were supposed > > to call periodically that would return false if the system felt that > > the CPU had done enough interrupts for the time being. In that case, > > the interrupt handler was supposed to schedule itself for a later time, > > but leave the interrupt unacknowledged in order to prevent retriggering > > in the meantime. > > > > Of course, this mechanism would be rather less helpful in Linux. > > > > For one, Linux has way more device drivers and way more oddball devices. > > In contrast, the few devices that DYNIX/ptx supported were carefully > > selected, and the selection criteria included being able to put up > > with this sort of thing. Also, the fact that there was but a handful > > of device drivers meant that changes like this could be more easily > > propagated through all drivers. > > We could do that completely at the core interrupt handling level. Ah, true enough if the various NAPI-like devices give up the CPU from time to time. Which they might well do for all I know. > > Also, Linux supports way more workloads. In contrast, DYNIX/ptx could > > pick a small percentage of each CPU that would be permitted to be used > > by hardware interrupt handlers. As in there are probably Linux workloads > > that run >90% of some poor CPU within hardware interrupt handlers. > > Yet another tunable. /me runs ;-) ;-) ;-) If there are workloads that would like to be able to keep one or more CPUs completely busy handling interrupts, it should be possible to create something that is used sort of like cond_resched() to keep RCU, the scheduler, and the various watchdogs and lockup detectors at bay. For example, RCU could supply a function that checked to make sure that it was in an interrupt from idle, and if so report a quiescent state for that CPU. So if the CPU was idle and there wasn't anything pending for it, that CPU could safely stay in a hardirq handler indefinitely. I suppose that the function should return an indication in cases such as interrupt from non-idle. Sort of like NO_HZ_FULL, but for hardirq handlers, and also allowing those handlers to use RCU read-side critical sections. Or we could do what all the cool kids do these days, namely just apply machine learning, thus automatically self-tuning in real time. /me runs... Thanx, Paul _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-06 20:39 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-29 3:39 [RFC PATCH] arm64: defconfig: Disable fine-grained task level IRQ time accounting Alison Wang 2020-07-29 3:39 ` Alison Wang 2020-07-29 8:40 ` Kurt Kanzenbach 2020-07-29 8:40 ` Kurt Kanzenbach 2020-07-29 8:50 ` [EXT] " Alison Wang 2020-07-29 8:50 ` Alison Wang 2020-07-29 9:49 ` Vladimir Oltean 2020-07-29 9:49 ` Vladimir Oltean 2020-07-30 7:23 ` Kurt Kanzenbach 2020-07-30 7:23 ` Kurt Kanzenbach 2020-07-30 8:22 ` Vladimir Oltean 2020-07-30 8:22 ` Vladimir Oltean 2020-08-03 8:04 ` Kurt Kanzenbach 2020-08-03 8:04 ` Kurt Kanzenbach 2020-08-03 8:16 ` Vladimir Oltean 2020-08-03 8:16 ` Vladimir Oltean 2020-08-03 9:51 ` Robin Murphy 2020-08-03 9:51 ` Robin Murphy 2020-08-03 11:38 ` Vladimir Oltean 2020-08-03 11:38 ` Vladimir Oltean 2020-08-03 11:48 ` Valentin Schneider 2020-08-03 11:48 ` Valentin Schneider 2020-08-03 13:24 ` Marc Zyngier 2020-08-03 13:24 ` Marc Zyngier 2020-08-03 10:02 ` Thomas Gleixner 2020-08-03 10:02 ` Thomas Gleixner 2020-08-03 10:49 ` Thomas Gleixner 2020-08-03 10:49 ` Thomas Gleixner 2020-08-03 11:41 ` Vladimir Oltean 2020-08-03 11:41 ` Vladimir Oltean 2020-08-03 15:13 ` Thomas Gleixner 2020-08-03 15:13 ` Thomas Gleixner 2020-08-03 15:47 ` Valentin Schneider 2020-08-03 15:47 ` Valentin Schneider 2020-08-03 16:14 ` Vladimir Oltean 2020-08-03 16:14 ` Vladimir Oltean 2020-08-03 19:22 ` Thomas Gleixner 2020-08-03 19:22 ` Thomas Gleixner 2020-08-03 23:59 ` Valentin Schneider 2020-08-03 23:59 ` Valentin Schneider 2020-08-05 8:50 ` Dietmar Eggemann 2020-08-05 8:50 ` Dietmar Eggemann 2020-08-05 13:40 ` peterz 2020-08-05 13:40 ` peterz 2020-08-05 13:56 ` Valentin Schneider 2020-08-05 13:56 ` Valentin Schneider 2020-08-05 15:31 ` peterz 2020-08-05 15:31 ` peterz 2020-08-06 9:41 ` Thomas Gleixner 2020-08-06 9:41 ` Thomas Gleixner 2020-08-06 11:45 ` peterz 2020-08-06 11:45 ` peterz 2020-08-06 13:27 ` Paul E. McKenney 2020-08-06 13:27 ` Paul E. McKenney 2020-08-06 19:03 ` Thomas Gleixner 2020-08-06 19:03 ` Thomas Gleixner 2020-08-06 20:39 ` Paul E. McKenney [this message] 2020-08-06 20:39 ` Paul E. McKenney 2020-08-06 18:58 ` Thomas Gleixner 2020-08-06 18:58 ` Thomas Gleixner 2020-08-06 9:34 ` Thomas Gleixner 2020-08-06 9:34 ` Thomas Gleixner
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200806203914.GQ4295@paulmck-ThinkPad-P72 \ --to=paulmck@kernel.org \ --cc=alison.wang@nxp.com \ --cc=anna-maria@linutronix.de \ --cc=catalin.marinas@arm.com \ --cc=kurt.kanzenbach@linutronix.de \ --cc=leoyang.li@nxp.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mw@semihalf.com \ --cc=olteanv@gmail.com \ --cc=peterz@infradead.org \ --cc=tglx@linutronix.de \ --cc=valentin.schneider@arm.com \ --cc=vladimir.oltean@nxp.com \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.