lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <ac37c63a5039435ab775a0e983213902@AcuMS.aculab.com> Date: Tue, 4 Oct 2022 10:45:43 +0000 From: David Laight <David.Laight@...LAB.COM> To: 'John Stultz' <jstultz@...gle.com>, LKML <linux-kernel@...r.kernel.org> CC: Pavankumar Kondeti <pkondeti@...eaurora.org>, John Dias <joaodias@...gle.com>, Connor O'Brien <connoro@...gle.com>, Rick Yiu <rickyiu@...gle.com>, John Kacur <jkacur@...hat.com>, Qais Yousef <qais.yousef@....com>, Chris Redpath <chris.redpath@....com>, "Abhijeet Dharmapurikar" <adharmap@...cinc.com>, Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>, Juri Lelli <juri.lelli@...hat.com>, "Vincent Guittot" <vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>, Steven Rostedt <rostedt@...dmis.org>, "Thomas Gleixner" <tglx@...utronix.de>, "kernel-team@...roid.com" <kernel-team@...roid.com>, Satya Durga Srinivasu Prabhala <satyap@...eaurora.org>, "J . Avila" <elavila@...gle.com> Subject: RE: [RFC PATCH v4 3/3] softirq: defer softirq processing to ksoftirqd if CPU is busy with RT From: John Stultz > Sent: 04 October 2022 00:21 > > From: Pavankumar Kondeti <pkondeti@...eaurora.org> > > Defer the softirq processing to ksoftirqd if a RT task is > running or queued on the current CPU. This complements the RT > task placement algorithm which tries to find a CPU that is not > currently busy with softirqs. > > Currently NET_TX, NET_RX, BLOCK and IRQ_POLL softirqs are only > deferred as they can potentially run for long time. Deferring NET_RX to ksoftirqd stops the NET_RX code from running until the RT process completes. This has exactly the same problems as the softint taking priority of the RT task - just the other way around. Under very high traffic loads receive packets get lost. In many cases that is actually far worse that the wakeup of an RT process being delayed slightly. The is no 'one size fits all' answer to the problem. Plausibly depending on the priority of the RT task might be useful. But sometimes it depends on the actual reason for the wakeup. For instance a wakeup from an ISR or a hish-res timer might need lower latency than one from a futex. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Powered by blists - more mailing lists