Kernels (简体中文)

From ArchWiki
Jump to: navigation, search
翻译状态: 本文是英文页面 Kernels翻译,最后翻译时间:2017-06-01,点击这里可以查看翻译后英文页面的改动。

来自 Wikipedia:


在Arch Linux中,除了官方内核之外,还有许多各种各样的内核可供选择。这篇文章列出了这些内核和它们的简短介绍。这里还列出了一些可用的内核补丁的介绍。在文章的最后介绍了自行编译内核的方法。



位于 "core" 仓库中,包含了对应的 Linux 内核和内核模块。官方原版内核再加 几个补丁.
更加注重安全的 Linux 内核,采用一系列 加固补丁 以减少内核和用户空间产生漏洞的风险。和 linux 相比,还启用了一些加固选项,比如用户命名空间(同时通过补丁禁用未授权用户的访问)、审计以及 SELinux
长期支持版 (LTS) 位于[core]仓库中,包含了长期支持的 Linux 内核和内核模块。
ZEN Kernel 是一些内核黑客合作的结果,提供了适合日常使用的优秀内核。

AUR 软件包

对于下面的 AUR 软件包,"预先编译" 意味着这些软件包被持续维护、测设和验证,有些软件包可以通过 Unofficial repositories 非官方软件仓库获取。

兼容 aufs 的 linux 内核及模块,适合使用 docker 的场景.
Linux 内核加 Con Kolivas 的 ck1 补丁。
通过 PKGBUILD 可以配置的功能包括: BFQ 调度器, nconfig, localmodconfig 和使用当前运行内核的 config。
The Linux Kernel and modules with fbcondecor support.
Linux kernel and modules built using sources from Linus Torvalds' Git repository.
The Linux Kernel and modules with gentoo-sources patchset and TuxOnIce support.
linux-libreAUR, linux-libre-ltsAUR, linux-libre-rtAUR, linux-libre-xenAUR
The Linux Kernels without "binary blobs".
Liquorix is a distro kernel replacement built using a Debian-targeted configuration and the ZEN kernel sources. Designed for desktop, multimedia, and gaming workloads, it is often used as a Debian Linux performance replacement kernel. Damentz, the maintainer of the Liquorix patchset, is a developer for the ZEN patchset as well.
The Linux 3.10 Long-Term Support Kernel and modules.
The Mainline Linux Kernel and modules.
The Linux Kernel and modules with Multipath TCP support.
Linux kernel and modules with the pf-kernel patch [-ck patchset (BFS included), TuxOnIce, BFQ] and aufs3.
Linux kernel with the realtime patch set. Improves latency and introduces hard realtime support.
The current/LTS Linux Kernel and modules with integrated TRESOR
The Linux kernel and a few patches written by Alex Williamson (acs override and i915) to enable the ability to do PCI Passthrough with KVM on some machines.


There are lots of reasons to patch your kernel, the major ones are for performance or support for non-mainline features such as reiser4 file system support. Other reasons might include fun and to see how it is done and what the improvements are.

However, it is important to note that the best way to increase the speed of your system is to first tailor your kernel to your system, especially the architecture and processor type. For this reason using pre-packaged versions of custom kernels with generic architecture settings is not recommended or really worth it. A further benefit is that you can reduce the size of your kernel (and therefore build time) by not including support for things you do not have or use. For example, you might start with the stock kernel config when a new kernel version is released and remove support for things like bluetooth, video4linux, 1000Mbit ethernet, etc.; functionality you know you will not require for your specific machine. Although this page is not about customizing your kernel config, it is recommended as a first step--before moving on to using a patchset once you have grasped the fundamentals involved.

The config files for the Arch kernel packages can be used as a starting point. They are in the Arch package source files, for example [1] linked from linux. The config file of your currently running kernel may also be available in your file system at /proc/config.gz if the CONFIG_IKCONFIG_PROC kernel option is enabled.


The installation process of custom kernel packages relies on the Arch Build System (ABS). If you have not built any custom packages yet you may consult the following articles: Arch Build System and Creating packages.

If you have not actually patched or customized a kernel before it is not that hard and there are many PKGBUILDs on the forum for individual patchsets. However, you are advised to start from scratch with a bit of research on the benefits of each patchset, rather than just arbitrarily picking one. This way you will learn much more about what you are doing rather than just choosing a kernel at startup and then be left wondering what it actually does.

See #编译.

Note: Do not forget to change the boot options in your bootloader, e.g. GRUB, to use the new kernel.


First of all it is important to note that patchsets are developed by a variety of people. Some of these people are actually involved in the production of the linux kernel and others are hobbyists, which may reflect its level of reliability and stability.

It is also worth noting that some patchsets are built on the back of other patchsets (which may or may not be reflected in the title of the patch). Patchsets (and kernel updates) can be released very frequently and often it is not worth keeping up with ALL of them; so, do not go crazy, unless you make it your hobby!

You can search Google for more sets, but remember to use quotes ("-nitro", for example); otherwise, Google will deliberately NOT show the results you want!

Note: This section is for information only - clearly no guarantees of stability or reliability are implied by inclusion on this page.


Linux-ck contains patches designed to improve system responsiveness with specific emphasis on the desktop, but suitable to any workload. The patches are created and maintained by Con Kolivas, his site is at Con maintains a full set but also provides the patches broken down so you can add only those you prefer.

The -ck patches can be found at


This patchset is maintained by a small group of core developers, led by Ingo Molnar. This patch allows nearly all of the kernel to be preempted, with the exception of a few very small regions of code ("raw_spinlock critical regions"). This is done by replacing most kernel spinlocks with mutexes that support priority inheritance, as well as moving all interrupt and software interrupts to kernel threads.

It further incorporates high resolution timers - a patch set, which is independently maintained.

[as said from the Real-Time Linux Wiki]

patch at


Warning: This patch is in development.

BLD is best described as a O(1) CPU picking technique. Which is done by reordering CPU runqueues based on runqueue loads. In other words, it keeps the scheduler aware of the load changes, which helps scheduler to keep runqueues in an order. This technique does not depend on scheduler ticks. The two most simple things in this technique are: load tracking and runqueue ordering; these are relatively simpler operations. Load tracking will be done whenever a load change happens on the system and based on this load change runqueue will be ordered. So, if we have an ordered runqueue from lowest to highest, then picking the less (or even busiest) runqueue is easy. Scheduler can pick the lowest runqueue without calculation and comparison at the time of placing a task in a runqueue. And while trying to distribute load at sched_exec and sched_fork our best choice is to pick the lowest busiest runqueue of the system. And in this way, system remains balanced without doing any load balancing. At the time of try_to_wake_up picking the idlest runqueue is topmost priority but it has been done as per domain basis to utilize CPU cache properly and it's an area where more concentration is requires.

Google Code web page:


The goal of Linux Tiny is to reduce its memory and disk footprint, as well as to add features to aid working on small systems. Target users are developers of embedded system and users of small or legacy machines such as 386s.

Patch releases against the mainstream Linux kernel have been discontinued. The developers chose to focus on a few patches and spend their time trying to get them merged into the mainline kernel.


linux-pfAUR is yet another Linux kernel fork which provides you with a handful of awesome features not merged into mainline. It is based on neither existing Linux fork nor patchset, although some unofficial ports may be used if required patches have not been released officially. The most prominent patches of linux-pf are TuxOnIce, the CK patchset (most notably BFS), AUFS3, LinuxIMQ, l7 filter and BFQ.

See linux-pf for more information.


这里有一些补丁可以直接应用在任何一个主流内核中,或加入到其它补丁集中(可能需要一些调整)。I have included some common ones for starters.






Arch Linux 提供了多种内核构建方式。

使用 Arch 构建系统(ABS)(推荐)

推荐使用 Arch 构建系统,这样可以充分利用已有的 linux PKGBUILD 以及包管理系统。PKGBUILD 已经是结构化的,你可以在下载源代码之后配置内核。

参见 编译内核/Arch 构建系统.


另外,也可以不使用 Arch 构建系统 编译内核(传统方式)。这个方法需要手动下载内核源代码包,然后在自己的主目录里以普通用户的权限编译。一旦完成配置之后,有两种编译(安装)方式:传统的安装和适用makepkg/pacman 的安装。


参见 传统方式 .