From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: linux5.5: consider switching from PREEMPT to PREEMPT_VOLUNTARY
Date: Mon, 10 Feb 2020 14:08:50 +0100 [thread overview]
Message-ID: <20200210130850.tHpL4PzbeObWCdcCc-wLGMjvBI6nwKDA3daTJeOFuXI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18940@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/18940#issuecomment-584114139
Comment:
```
1. Never omit scheduling-clock ticks (CONFIG_HZ_PERIODIC=y or CONFIG_NO_HZ=n for older kernels). You normally will -not- want to choose this option.
2. Omit scheduling-clock ticks on idle CPUs (CONFIG_NO_HZ_IDLE=y or CONFIG_NO_HZ=y for older kernels). This is the most common approach, and should be the default.
3. Omit scheduling-clock ticks on CPUs that are either idle or that have only one runnable task (CONFIG_NO_HZ_FULL=y). Unless you are running realtime applications or certain types of HPC workloads, you will normally -not- want this option.
```
Sounds like our config is correct already.
next prev parent reply other threads:[~2020-02-10 13:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 15:01 [ISSUE] " voidlinux-github
2020-02-09 15:49 ` voidlinux-github
2020-02-09 16:28 ` voidlinux-github
2020-02-09 16:29 ` voidlinux-github
2020-02-09 22:53 ` voidlinux-github
2020-02-09 23:14 ` voidlinux-github
2020-02-10 7:29 ` voidlinux-github
2020-02-10 7:44 ` voidlinux-github
2020-02-10 8:12 ` voidlinux-github
2020-02-10 8:22 ` voidlinux-github
2020-02-10 8:34 ` voidlinux-github
2020-02-10 9:21 ` voidlinux-github
2020-02-10 10:34 ` voidlinux-github
2020-02-10 13:08 ` voidlinux-github [this message]
2020-02-10 13:09 ` voidlinux-github
2020-02-10 14:10 ` voidlinux-github
2020-02-10 14:15 ` voidlinux-github
2020-02-11 9:08 ` voidlinux-github
2020-02-11 9:17 ` voidlinux-github
2020-02-11 11:10 ` voidlinux-github
2020-02-11 11:13 ` voidlinux-github
2020-02-11 16:59 ` voidlinux-github
2020-02-11 17:40 ` voidlinux-github
2020-02-11 17:41 ` voidlinux-github
2020-02-12 14:14 ` [ISSUE] [CLOSED] " voidlinux-github
2020-02-12 14:14 ` voidlinux-github
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=20200210130850.tHpL4PzbeObWCdcCc-wLGMjvBI6nwKDA3daTJeOFuXI@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).