From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 25B2DC02192 for ; Sun, 2 Feb 2025 03:26:34 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 81ED76B007B; Sat, 1 Feb 2025 22:26:33 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 7CF026B0083; Sat, 1 Feb 2025 22:26:33 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 697356B0085; Sat, 1 Feb 2025 22:26:33 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id 43C996B007B for ; Sat, 1 Feb 2025 22:26:33 -0500 (EST) Received: from smtpin25.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay04.hostedemail.com (Postfix) with ESMTP id B9B9D1A1DCD for ; Sun, 2 Feb 2025 03:26:32 +0000 (UTC) X-FDA: 83073567024.25.77E8F49 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf10.hostedemail.com (Postfix) with ESMTP id 2681AC0009 for ; Sun, 2 Feb 2025 03:26:31 +0000 (UTC) Authentication-Results: imf10.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf10.hostedemail.com: domain of "SRS0=SoZy=UZ=goodmis.org=rostedt@kernel.org" designates 139.178.84.217 as permitted sender) smtp.mailfrom="SRS0=SoZy=UZ=goodmis.org=rostedt@kernel.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1738466791; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MvhHTVYuGcNz69qQApwGJaaipdCpQtjKyE5AZ6KAfSA=; b=fcU1EEnoGwIZrC6TdKANywe7NC8eUsx9tBIMLSLa+u+ZsnlRNdW+LB33WSiKGP713y4spr LCu87z90KkZ4iMxOtCo0m6MPE9aObc3A9L7qgPdyRufU5drrsUEk3nXaRMEbItwxr/KqSJ s2DUKlb946O7LgIhpGIwVzSS+72HDQo= ARC-Authentication-Results: i=1; imf10.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf10.hostedemail.com: domain of "SRS0=SoZy=UZ=goodmis.org=rostedt@kernel.org" designates 139.178.84.217 as permitted sender) smtp.mailfrom="SRS0=SoZy=UZ=goodmis.org=rostedt@kernel.org" ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1738466791; a=rsa-sha256; cv=none; b=7Nnt/ZVOlf0XvjnX+8wIzrQMqBAiS7LStAdL6JuHx1BG2kr1ZEOphNakL/n+y2aA8KSat6 jUAZfwua7GrzxRLCpbSEjf+EH/tbP+DVUbZT4F6Kn8kDWG/HPtdzWUnXUB9aQok8Eis89a L9q0T4FvQhXG4s/bqnfnBDxnhdHKClY= Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id D90F15C4B3C; Sun, 2 Feb 2025 03:25:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EBDB2C4CED1; Sun, 2 Feb 2025 03:26:25 +0000 (UTC) Date: Sat, 1 Feb 2025 22:26:24 -0500 From: Steven Rostedt To: Linus Torvalds Cc: Mathieu Desnoyers , linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org, Thomas Gleixner , Peter Zijlstra , Ankur Arora , linux-mm@kvack.org, x86@kernel.org, akpm@linux-foundation.org, luto@kernel.org, bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com, juri.lelli@redhat.com, vincent.guittot@linaro.org, willy@infradead.org, mgorman@suse.de, jon.grimm@amd.com, bharata@amd.com, raghavendra.kt@amd.com, boris.ostrovsky@oracle.com, konrad.wilk@oracle.com, jgross@suse.com, andrew.cooper3@citrix.com, Joel Fernandes , Vineeth Pillai , Suleiman Souhlal , Ingo Molnar , Clark Williams , bigeasy@linutronix.de, daniel.wagner@suse.com, joseph.salisbury@oracle.com, broonie@gmail.com Subject: Re: [RFC][PATCH 1/2] sched: Extended scheduler time slice Message-ID: <20250201222624.61722cdb@batman.local.home> In-Reply-To: References: <20250131225837.972218232@goodmis.org> <20250131225942.365475324@goodmis.org> <20250201180810.1faf4906@batman.local.home> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 2681AC0009 X-Stat-Signature: qjo7cnpbcazfwe6xm9e3r9g8zqfxzejx X-Rspam-User: X-HE-Tag: 1738466791-301698 X-HE-Meta: U2FsdGVkX1/7fVKbuiOOljGTYTmm6Bqh5GEISsw2TBPCeRaDzRgw0XoD1s9+CM/JwljHMZP0m/VQVFcB7TLwntHjlvVYBR8RUt+p5aH4Vab4BAGItoIQdqDwgJzocgfgIBhRHOTswIrweb6XN1wyxRTUhaT/QgjeqmwupQgmcVPtFGLHattBmHXJXqBKlVB+3x4CJmxZqJnqNHpI9hv4TXzsjGi69Bb27/o95l6KLDtXpA7WO1E92ideDxoEW64pIVRoZCc4atgty927e5ikCWa2CawEls4gWLT305uA64km68PTsiiLXwBYvtUZq+Dkvvd/rFB5oZpsBH+0Jrif+kHEED7XiB6XfY/rH765H6779gWPmNbmkrDCU4N0E29zJ4XGcmTtHlDywB4Ty6XcfYr0PUiki5AAB4X5D3NOULDo9zsLtpRd2GQJyaCFfrv0XGlbnB0O/6d1ZABlYHrMexVh231f4BDRTtWRxmixhuzrXnpgzUp7qwno0GrP8d+1B9+I2dvVN1jiIHtk224wcsnRdBu9pb79SY5z8J+LQGDtYE24WiKt3Lc3MpZYfFQzI5/KzzaLzZwhbluhTuepVdm+AciTdYlEYMC5wv/q5QVbOOuJFVVUoPnuLzSaMFmW8UkttvoGaLBLj/qloHyi2WTh24Bgb796sMboQLlt/T36A/rBqKCbfro9lI8LhFBUSPHZv+bmzxySJATj56AftBDH2kAZTG0s2D/94bZgMUezPwUlxm0nDGjzZCZ87uVwVM+Ux0hNt2BBErJ8yTVLZBfMJN3SBnD8lwyhgdpBa5yamC2ucX/RRjOUOM7EHoLSHlsJqvnDuJ/bxvCkBQAedUMQjRbeVLAxneejFdPd0vdPC7IF+UYdGeyG2z3v6ZAu66+WnswB7TGZJxtD0lYHD8XjRHGg/Ds2NSIwnIAT/Uv64XEMYY48tDfqF36QR4/cFzjbMFEv1CaRsOo6w5v ttA8cBH6 rp+BWiV1026iVUXjRbF5PAgmYZ61Q55A4XFDYndEWQ9ISaZDJ1ho+NxxVEAL82w72uAJFmE6gYGYE74CsmqZU80Qz5n/K8b1mHtFbk6Z3R9dDsATHGZUAIDWMDa3xMpsU2rK8tT3f2vfWoC8ehWAo+TYMm6aYztx1DTfGCHxmVr6JeMJdEw+dxWieTqD2SYZmc2CGEjbogtKhbGu79DZsnM8lzfZ26EAbXab5do9QSQucVrgTzvs6/R1FpO/rzS0hRtezPwHGUxJ9IzNJPxkVvZGUOgWjg/wKgnj75hO6M18zhul8yzAYb4hiT+/e1B9HBHBF5yMQ2aD9lFC9kzOHyXRB461lvdAr8J5RynuxxsUJIXgjk4ZsgJTTYHvZnp/Mjhsa X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Sat, 1 Feb 2025 15:35:53 -0800 Linus Torvalds wrote: > I didn't actually check what current active schedulers do. I would > not be in the least surprised if different schedulers end up having > very different behavior (particularly any RT scheduler). The only real use of sched yield() I have ever seen in practice was in a RT application where all tasks were given the same RT FIFO priority, and the application would use the yield() system call to trigger the next task. That's also the only use case that really does have a strict defined behavior for yield(). In SCHED_FIFO, as the name suggests, tasks run in a first-in first-out order. yield() will put the task at the end of that queue. You can use this method to implement a strict application defined scheduler. -- Steve.