all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: kiasoc5 <kiasoc5@disroot.org>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Linux 6.12 new preemption models
Date: Fri, 3 Jan 2025 13:15:42 -0500	[thread overview]
Message-ID: <984fd7bf-40e2-4617-89e4-8fd488e47840@disroot.org> (raw)
In-Reply-To: <Z3XG5EcJurB8W8cG@jasmine.lan>

On 1/1/25 17:51, Leo Famulari wrote:
> FYI, Linux / linux-libre 6.12 introduces a new set of preemption
> options:
> 
> ------
> Preemption Model
>    1. No Forced Preemption (Server) (PREEMPT_NONE)
>> 2. Voluntary Kernel Preemption (Desktop) (PREEMPT_VOLUNTARY)
>    3. Preemptible Kernel (Low-Latency Desktop) (PREEMPT)
>    4. Fully Preemptible Kernel (Real-Time) (PREEMPT_RT) (NEW)
> ------
> 
> These options trade between kernel throughput and latency.
> 
> PREEMPT_NONE is how the kernels worked before 6.12.
> 
> The trade-off made in PREEMPT_VOLUNTARY is suggested for desktops, so
> I'm going to select it for our 6.12 kernel packaging and it will
> presumably remain so for future versions as well.
> 
> But if you are building Guix kernels for a busy server or HPC, you
> should select PREEMPT_NONE. And you might have use cases for the other
> options as well.
> 
> Let me know if you disagree.
> 
> References:
> https://cateee.net/lkddb/web-lkddb/PREEMPT_NONE.html
> https://cateee.net/lkddb/web-lkddb/PREEMPT_VOLUNTARY.html
> https://cateee.net/lkddb/web-lkddb/PREEMPT.html
> https://cateee.net/lkddb/web-lkddb/PREEMPT_RT.html
> 


How about PREEMPT_DYNAMIC: 
https://cateee.net/lkddb/web-lkddb/PREEMPT_DYNAMIC.html

This enables changing between PREEMPT_NONE, PREEMPT_VOLUNTARY, and 
PREEMPT at boot time. Then the only kernel that needs to be compiled 
separate is PREEMPT_RT.


  reply	other threads:[~2025-01-03 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-01 22:51 Linux 6.12 new preemption models Leo Famulari
2025-01-03 18:15 ` kiasoc5 [this message]
2025-01-03 18:21   ` Leo Famulari

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=984fd7bf-40e2-4617-89e4-8fd488e47840@disroot.org \
    --to=kiasoc5@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.