linux-kernel - Re: [RFC][PATCH 1/2] sched: Extended scheduler time slice

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250210122700.3b963ff0@gandalf.local.home>
Date: Mon, 10 Feb 2025 12:27:00 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: David Laight <david.laight.linux@...il.com>
Cc: Joel Fernandes <joel@...lfernandes.org>, Prakash Sangappa
 <prakash.sangappa@...cle.com>, Peter Zijlstra <peterz@...radead.org>,
 linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Thomas
 Gleixner <tglx@...utronix.de>, Ankur Arora <ankur.a.arora@...cle.com>,
 Linus Torvalds <torvalds@...ux-foundation.org>, linux-mm@...ck.org,
 x86@...nel.org, Andrew Morton <akpm@...ux-foundation.org>, luto@...nel.org,
 bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com,
 juri.lelli@...hat.com, vincent.guittot@...aro.org, willy@...radead.org,
 mgorman@...e.de, jon.grimm@....com, bharata@....com,
 raghavendra.kt@....com, Boris Ostrovsky <boris.ostrovsky@...cle.com>,
 Konrad Wilk <konrad.wilk@...cle.com>, jgross@...e.com,
 Andrew.Cooper3@...rix.com, Vineeth Pillai <vineethrp@...gle.com>, Suleiman
 Souhlal <suleiman@...gle.com>, Ingo Molnar <mingo@...nel.org>, Mathieu
 Desnoyers <mathieu.desnoyers@...icios.com>, Clark Williams
 <clark.williams@...il.com>, bigeasy@...utronix.de, daniel.wagner@...e.com,
 Joseph Salisbury <joseph.salisbury@...cle.com>, broonie@...il.com
Subject: Re: [RFC][PATCH 1/2] sched: Extended scheduler time slice

On Mon, 10 Feb 2025 17:20:59 +0000
David Laight <david.laight.linux@...il.com> wrote:

> Hmmm... you lose big-time anyway.
> 
> All you need is a lot of network traffic 'pinch' the process context until
> the hardware interrupt, NAPI softint code and rcu softint code completes.
> That can easily take several milliseconds.

Not on PREEMPT_RT. All that runs as threads.

And this is a feature that we would like on RT for non RT tasks.

-- Steve