Difference between revisions of "Linux-ck"
(→Release cycle: update criteria for release) |
(virtualbox-ck-host-modules is orphaned) |
||
(46 intermediate revisions by 13 users not shown) | |||
Line 2: | Line 2: | ||
[[ja:Linux-ck]] | [[ja:Linux-ck]] | ||
[[ru:Linux-ck]] | [[ru:Linux-ck]] | ||
− | [[zh- | + | [[zh-hans:Linux-ck]] |
{{Related articles start}} | {{Related articles start}} | ||
− | {{Related| | + | {{Related|Unofficial user repositories/Repo-ck}} |
− | |||
{{Related|Modprobed-db}} | {{Related|Modprobed-db}} | ||
{{Related articles end}} | {{Related articles end}} | ||
Line 11: | Line 10: | ||
== General package details == | == General package details == | ||
− | {{AUR|Linux-ck}} is a package available in | + | {{AUR|Linux-ck}} is a package available both in [[AUR]] and in the [[#Use pre-compiled packages|unofficial repo-ck repository]] that allows users to run a kernel and headers setup patched with Con Kolivas' ck patchset[http://ck.kolivas.org/patches/], including a CPU scheduler named MuQSS (''Multiple Queue Skiplist Scheduler'', pronounced ''mux'') which replaces Brain Fuck Scheduler (BFS), his previous work. Many Arch Linux users choose this kernel for its excellent desktop interactivity and responsiveness under any load situation. |
+ | |||
+ | CK patchset is designed for desktop/laptop use but not for servers. It provides low latency environment and works well for 16 CPUs or fewer. | ||
=== Release cycle === | === Release cycle === | ||
− | Linux-ck roughly follows the release cycle of the official | + | Linux-ck roughly follows the release cycle of the official Arch kernel but not only. The following are requirements for a new package release: |
− | * | + | * CK patchset compatible with the current kernel version |
− | + | * corresponding Arch kernel must be in existence otherwise it will break other packages i.e. nvidia. See [https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/linux git.archlinux.org] for the official {{Pkg|linux}} package | |
− | |||
=== Package defaults === | === Package defaults === | ||
There are '''three''' modifications to the config files: | There are '''three''' modifications to the config files: | ||
− | # The options that the | + | # The options that the CK patchset enable/disable. |
− | # The | + | # The tickrate is set to 100 Hz (CK's recommendation). |
− | # | + | # The extra CPU types optionally available to compilation thanks to the [https://github.com/graysky2/kernel_gcc_patch GCC patch]. |
+ | |||
+ | '''All other options are set to the Arch defaults outlined in the main kernel's config files.''' Of course users are free to edit them. | ||
− | + | The {{AUR|linux-ck}} package contains an option to switch on the '''nconfig''' config editor (see the section [[#Compile the package from source|below]]). | |
=== Long-Term Support (LTS) CK releases === | === Long-Term Support (LTS) CK releases === | ||
− | In addition to the linux-ck package, there are | + | In addition to the {{AUR|linux-ck}} package, there are LTS kernel releases patched with the above patchsets as well and with the previously mentioned modifications: |
− | * {{AUR|linux-lts-ck}} - The current | + | * {{AUR|linux-lts-ck}} - The current Arch Linux LTS kernel patched with the CK patchset |
− | |||
− | |||
− | + | {{Note|This package is maintained by vishwin, thus pre-compiled versions will not be present in the unofficial ck repo.}} | |
== Installation options == | == Installation options == | ||
− | {{Note|As with ''any'' additional kernel, users | + | {{Note|As with ''any'' additional kernel, users need to manually update their [[boot loader]]'s configuration file in order to make it aware of the new kernel image.}} |
Users have two options to get these kernel packages. | Users have two options to get these kernel packages. | ||
Line 50: | Line 50: | ||
The [[AUR]] contains entries for both packages mentioned above. | The [[AUR]] contains entries for both packages mentioned above. | ||
− | Users can customize the linux-ck package via tweaks in the PKGBUILD: | + | Users can further customize the linux-ck package via tweaks contained in the PKGBUILD: |
− | * Optional nconfig for user specific tweaking. | + | * Optional '''nconfig''' for user specific tweaking. |
− | * Option to compile a minimal set of modules via a make localmodconfig. | + | * Option to compile a minimal set of modules via a make '''localmodconfig'''. |
− | * Option to bypass the standard | + | * Option to bypass the standard Arch config options and simply use the '''current kernel configuration''' file. |
* Optionally set the [http://algo.ing.unimo.it/people/paolo/disk_sched/ BFQ I/O scheduler] as default. | * Optionally set the [http://algo.ing.unimo.it/people/paolo/disk_sched/ BFQ I/O scheduler] as default. | ||
− | More details about these options are provided in the PKGBUILD itself | + | More details about these options are provided in the PKGBUILD itself. Be sure to read them carefully if compiling from AUR! |
− | {{Note|There are related PKGBUILDs in | + | {{Note|There are the related PKGBUILDs in AUR for other common kernel modules. For example {{AUR|nvidia-ck}}, {{AUR|nvidia-340xx-ck}}, and {{AUR|broadcom-wl-ck}} to name a few. Alternatively, use the corresponding [[DKMS]] package, for instance install {{pkg|nvidia-dkms}} as described in [[NVIDIA#Custom kernel]].}} |
=== Use pre-compiled packages === | === Use pre-compiled packages === | ||
− | If | + | If user prefers to spend no time to compile on their own, the unofficial repo maintained by [[User:Graysky|graysky]] is available to the community. For details, see: [[Unofficial user repositories/Repo-ck]]. |
− | |||
− | |||
== How to enable the BFQ I/O Scheduler == | == How to enable the BFQ I/O Scheduler == | ||
− | |||
− | Budget Fair Queueing is a | + | {{Note|Do not confuse MuQSS (Multiple Queue Skiplist Scheduler) with BFQ (Budget Fair Queueing). MuQSS is a CPU scheduler and is enabled by default whereas BFQ is an I/O scheduler and must explicitly be enabled in order to use it.}} |
− | + | See the [[Improving performance#Input/output schedulers]] section for some background about the different IO schedulers and how to activate ''BFQ''. | |
− | == | + | == More about MuQSS == |
− | + | See the [https://lkml.org/lkml/2016/10/29/4 LKML announcement] posted by CK. | |
− | |||
− | + | === Check if MuQSS is enabled === | |
− | + | This start-up message should appear in the kernel ring buffer when MuQSS in enabled: | |
+ | $ dmesg | grep -i muqss | ||
+ | ... | ||
+ | MuQSS CPU scheduler v0.120 by Con Kolivas. | ||
− | + | === MuQSS patched kernels and systemd === | |
− | |||
− | + | It is a common mistake to think that MuQSS does not support ''cgroups''. It does but not all the cgroup features (e.g. CPU limiting will not work). | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Troubleshooting == | == Troubleshooting == | ||
Line 98: | Line 90: | ||
=== Running VirtualBox with Linux-ck === | === Running VirtualBox with Linux-ck === | ||
− | VirtualBox works just fine with custom kernels such as Linux-ck ''without'' the need to keep any of the official | + | VirtualBox works just fine with custom kernels such as Linux-ck ''without'' the need to keep any of the official Arch kernel headers package on the system. |
Do not forget to add users to the ''vboxusers '' group: | Do not forget to add users to the ''vboxusers '' group: | ||
# gpasswd -a USERNAME vboxusers | # gpasswd -a USERNAME vboxusers | ||
− | ==== Use the unofficial repo (recommended if | + | ==== Use the unofficial repo (recommended if Linux-ck is installed from Repo-ck) ==== |
− | {{Note|As of 17-Oct-2012, Repo-ck users can enjoy these modules as pre-compiled packages in the repo itself. | + | {{Note|As of 17-Oct-2012, Repo-ck users can enjoy these modules as pre-compiled packages in the repo itself. If you build Linux-ck from AUR you '''can not use the repo''' as all packages in the repo are matched groups.}} |
− | See the [[Repo-ck]] | + | See the [[Unofficial user repositories/Repo-ck]] to set up it correctly. |
− | ==== | + | ==== DKMS ==== |
− | + | Install '''virtualbox''' with the '''virtualbox-host-dkms''' package. Then setup DKMS as follows: | |
− | |||
− | |||
− | |||
− | Install '''virtualbox''' with the '''virtualbox-host-dkms''' package. | ||
# pacman -S virtualbox virtualbox-host-dkms | # pacman -S virtualbox virtualbox-host-dkms | ||
− | |||
− | |||
− | |||
=== Downgrading === | === Downgrading === | ||
− | Users wishing to downgrade to a previous version of | + | Users wishing to downgrade to a previous version of Linux-ck, have several options: |
* Source archives are [http://repo-ck.com/bench.htm available] dating back to linux-ck-3.3.7-1. | * Source archives are [http://repo-ck.com/bench.htm available] dating back to linux-ck-3.3.7-1. | ||
− | * [http://pkgbuild.com/git/aur-mirror.git/log/linux-ck AUR.git] holds AUR git commits for | + | * [http://pkgbuild.com/git/aur-mirror.git/log/linux-ck AUR.git] holds AUR git commits for Linux-ck, dating back to linux-ck-2.6.39.3-1. |
=== Forum support === | === Forum support === | ||
− | Always feel free to open a thread in the forums for support. | + | Always feel free to open a thread in the forums for support purpose. Be sure to give the thread a descriptive title to draw attention to the fact that the post relates to the Linux-ck package. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | == | + | == See also == |
− | * [http://ck.kolivas.org/patches/ | + | * [http://ck.kolivas.org/patches/ Kernel patch repository of Con Kolivas] |
− | * [[wikipedia: | + | * [http://ck-hack.blogspot.it/ Con Kolivas' Blog] |
− | * [ | + | * [http://lkml.org/lkml/2009/9/6/136 Con Kolivas' first BFS announcement on the Linux Kernel Mailing List] |
+ | * [[wikipedia:Con_Kolivas|Wikipedia's Con Kolivas page]] | ||
+ | * [[wikipedia:Brain_Fuck_Scheduler|Wikipedia's BFS article]] |
Revision as of 19:24, 17 May 2018
Contents
General package details
Linux-ckAUR is a package available both in AUR and in the unofficial repo-ck repository that allows users to run a kernel and headers setup patched with Con Kolivas' ck patchset[1], including a CPU scheduler named MuQSS (Multiple Queue Skiplist Scheduler, pronounced mux) which replaces Brain Fuck Scheduler (BFS), his previous work. Many Arch Linux users choose this kernel for its excellent desktop interactivity and responsiveness under any load situation.
CK patchset is designed for desktop/laptop use but not for servers. It provides low latency environment and works well for 16 CPUs or fewer.
Release cycle
Linux-ck roughly follows the release cycle of the official Arch kernel but not only. The following are requirements for a new package release:
- CK patchset compatible with the current kernel version
- corresponding Arch kernel must be in existence otherwise it will break other packages i.e. nvidia. See git.archlinux.org for the official linux package
Package defaults
There are three modifications to the config files:
- The options that the CK patchset enable/disable.
- The tickrate is set to 100 Hz (CK's recommendation).
- The extra CPU types optionally available to compilation thanks to the GCC patch.
All other options are set to the Arch defaults outlined in the main kernel's config files. Of course users are free to edit them.
The linux-ckAUR package contains an option to switch on the nconfig config editor (see the section below).
Long-Term Support (LTS) CK releases
In addition to the linux-ckAUR package, there are LTS kernel releases patched with the above patchsets as well and with the previously mentioned modifications:
- linux-lts-ckAUR - The current Arch Linux LTS kernel patched with the CK patchset
Installation options
Users have two options to get these kernel packages.
Compile the package from source
The AUR contains entries for both packages mentioned above.
Users can further customize the linux-ck package via tweaks contained in the PKGBUILD:
- Optional nconfig for user specific tweaking.
- Option to compile a minimal set of modules via a make localmodconfig.
- Option to bypass the standard Arch config options and simply use the current kernel configuration file.
- Optionally set the BFQ I/O scheduler as default.
More details about these options are provided in the PKGBUILD itself. Be sure to read them carefully if compiling from AUR!
Use pre-compiled packages
If user prefers to spend no time to compile on their own, the unofficial repo maintained by graysky is available to the community. For details, see: Unofficial user repositories/Repo-ck.
How to enable the BFQ I/O Scheduler
See the Improving performance#Input/output schedulers section for some background about the different IO schedulers and how to activate BFQ.
More about MuQSS
See the LKML announcement posted by CK.
Check if MuQSS is enabled
This start-up message should appear in the kernel ring buffer when MuQSS in enabled:
$ dmesg | grep -i muqss ... MuQSS CPU scheduler v0.120 by Con Kolivas.
MuQSS patched kernels and systemd
It is a common mistake to think that MuQSS does not support cgroups. It does but not all the cgroup features (e.g. CPU limiting will not work).
Troubleshooting
Running VirtualBox with Linux-ck
VirtualBox works just fine with custom kernels such as Linux-ck without the need to keep any of the official Arch kernel headers package on the system.
Do not forget to add users to the vboxusers group:
# gpasswd -a USERNAME vboxusers
Use the unofficial repo (recommended if Linux-ck is installed from Repo-ck)
See the Unofficial user repositories/Repo-ck to set up it correctly.
DKMS
Install virtualbox with the virtualbox-host-dkms package. Then setup DKMS as follows:
# pacman -S virtualbox virtualbox-host-dkms
Downgrading
Users wishing to downgrade to a previous version of Linux-ck, have several options:
- Source archives are available dating back to linux-ck-3.3.7-1.
- AUR.git holds AUR git commits for Linux-ck, dating back to linux-ck-2.6.39.3-1.
Forum support
Always feel free to open a thread in the forums for support purpose. Be sure to give the thread a descriptive title to draw attention to the fact that the post relates to the Linux-ck package.