/explore
|
You are here 
|
lwn.net | ||
| | | | |
www.kroah.com
|
|
| | | | | Note This post is based on a whitepaper I wrote at the beginning of 2016 to be used to help many different companies understand the Linux kernel release model and encourage them to start taking the LTS stable updates more often. I then used it as a basis of a presentation I gave at the Linux Recipes conference in September 2017 which can be seen here. With the recent craziness of Meltdown and Spectre , I've seen lots of things written about how Linux is released and how we handle handles security patches that are totally incorrect, so I figured it is time to dust off the text, update it in a few places, and publish this here for everyone to benefit from. | |
| | | | |
www.linaro.org
|
|
| | | | | The Linux kernel development community is largely built around collaboration and communication. In last week's blog we talked about how to submit a patch. In this blog - the second part of our blog series on how to become a Kernel Developer - we talk about how to work effectively with the Linux kernel community. | |
| | | | |
hubris.oxide.computer
|
|
| | | | | ||
| | | | |
blog.nelhage.com
|
|
| | | tl;dr "Transparent Hugepages" is a Linux kernel feature intended to improve performance by making more efficient use of your processor's memory-mapping hardware. It is enabled ("enabled=always") by default in most Linux distributions. Transparent Hugepages gives some applications a small performance improvement (~ 10% at best, 0-3% more typically), but can cause significant performance problems, or even apparent memory leaks at worst. To avoid these problems, you should set enabled=madvise on your server... | ||
