Slashdot Mirror
Linux 4.18 Preparing Many New Features While Dropping 100k+ Lines of Code (phoronix.com)
An anonymous reader writes: Linux 4.18 development is going strong with recent 4.18-rc1 release. This kernel cycle has dropped 107,210 lines of code so far but Linux 4.18 is adding many new features. The kernel is coming in lighter as a result of the LustreFS code being removed and other code cleanups. On the feature front, Phoronix reports, "ew AMDGPU support improvements, mainlining of the V3D DRM driver, initial open-source work on NVIDIA Volta GV100 hardware, merging of the Valve Steam Controller kernel driver, merging of the BPFILTER framework, ARM Spectre mitigation work, Speck file-system encryption support, removal of the Lustre file-system, the exciting restartable sequences system call was merged, the new DM writecache target, and much more."
The Lustre devs basically never played nice with the Linux Kernel devs, and Lustre never left the STAGING sub-section of the Linux Kernel because they never (in almost a decade) cleaned up the code to pass Linux Kernel code reviews.
Lustre's most recent full release was just this last April, it's very much under heavy development, but in the HPC world having your code 'upstream' is basically a non-issue because they're used to having to do a million minor adjustments to eek out another 1% performance, since at the scale of computing they're doing that tiny improvement makes a noticeable difference. They don't run 'out of the box' Linux distros compared to a web-server or the like.
- WolfWings, too lazy to login to /. in far too long.
In this case what was removed was mostly components in the staging sub-section that had been there for years (over half a decade in many cases) but hadn't completed appreciable work towards exiting the Staging sub-section. So they're finally getting the boot back out of kernel since they had never graduated to 'full kernel support' due to lack of action on their devs part. Lustre in particular basically stopped contributing to the staging branch since they felt it slowed them down too much versus working on their out-of-tree version of the code instead.
How can I tell if the bug that was crashing Ryzen processors at idle has been fixed?
In 4,15, Ryzen users had to put in a boot option
"rcu_nocbs=0-15
(this case for 8 cores =0-11 for a six core...)
I had this problem too and the rcu_nocbs=0-15 didn't fix entirely the problem. You need zenstates to turn off the C6 power saving state.
Here's the systemd unit file:
[Unit]
/usr/local/src/ZenStates-Linux-master/zenstates.py --c6-disable
Description=Turn off power saving C6 state
[Service]
Type=oneshot
StandardOutput=syslog
ExecStart=/usr/bin/python
[Install]
WantedBy=basic.target