Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Linux

What's New in Linux 6.5? (9to5linux.com) 39

An anonymous reader shared this report from 9to5Linux: Just a couple of days after celebrating its 32nd anniversary , Linus Torvalds announced today the final release of the Linux 6.5 kernel series as a major update that introduces several new features, updated and new drivers for better hardware support, and other changes.

After seven weeks of RCs, Linux kernel 6.5 is here with new features like MIDI 2.0 support in ALSA, ACPI support for the RISC-V architecture, Landlock support for UML (User-Mode Linux), better support for AMD "Zen" systems, as well as user-space support for the ARMv8.8 memcpy/memset instructions. Also new in Linux 6.5 is Intel TPMI (Topology Aware Register and PM Capsule Interface) support for the power capping subsystem and a TPMI interface driver for Intel RAPL, and the "runnable boosting" feature in the EAS balancer to improve CPU utilization for specific workloads.

This release also improves SMP scheduling's load balancer to recognize SMT cores with more than one busy sibling and allows lower-priority CPUs to pull tasks to avoid superfluous migrations, and improves EXT4 file system's journalling, block allocator subsystems, and performance for parallel DIO overwrites.

This discussion has been archived. No new comments can be posted.

What's New in Linux 6.5?

Comments Filter:
  • Phoronix (Score:4, Informative)

    by bill_mcgonigle ( 4333 ) * on Sunday August 27, 2023 @07:26PM (#63802236) Homepage Journal
  • PulseAudio has always been terrible for me. Random beeps. Terrible background static. Randomly drops output and have to restart the server.
  • It has been forever that BTRFS was going to support write hole-less RAID-5/6. Like more than 7 years. But, checking the following site still shows RAID-5/6 as unstable.
    BTRFS - Status [readthedocs.io]

    So, back to the competition, the one that must not be named unless flame wars are desired.
    • No, the write-hole appears to still be present. Personally, I am keeping an eye on bcachefs as a possible replacement, since it seems to have the benefit of not having that issue. It's also got other benefits, like e.g. it doesn't require an out-of-tree module, like ZFS does. I've also found a rather big issue with Btrfs where you can hard-crash the Btrfs-driver in the kernel by using mergerfs with individual Btrfs-formatted drives/partitions (tested with kernels 5.15, 5.16 and 6.2 under Ubuntu), so I've be
      • it doesn't require an out-of-tree module, like ZFS does.

        What do you see as a drawback of an out of tree module?

        • it doesn't require an out-of-tree module, like ZFS does.

          What do you see as a drawback of an out of tree module?

          Not me, personally, but rather kernel-devs seem to have quite a lot of animosity towards such, including ZFS. Also I've seen some random negative ramblings from distro/package maintainers about it. I've never bothered to really read what all the hubbub was about as it's not really relevant for my interests, but my impression is that it has a tendency of causing quite a lot of friction in getting stuff fixed/improved and such.

          • Somehow ZFS seems to work great with Ubuntu (you can select root on encrypted ZFS as an install time option) and fine with Debian (you have to do the install on ZFS manually, but it works once you do so.) I've been using it for some time now through several kernel upgrades and one ZFS upgrade without any problems whatsoever.

            If other distributions have trouble integrating it, perhaps they should read some of the documentation on the OpenZFS website.

            • I don't necessarily disagree with you. I haven't used ZFS myself, but I've just been looking into it as I was planning to possibly switch my servers to it from Btrfs until bcachefs matures some more. Also, I was thinking of throwing together a TrueNAS Scale setup from leftover parts and that uses ZFS as well, so I've got a reasonable excuse to learn all about it.
    • by gweihir ( 88907 )

      Use md raid? You know, like a sane person?

    • RAID 5/6 is, for large modern hard drives, unsafe on any file system. I personally prefer using RAID 1c3 for both data and metadata on BTRFS.

      • Same. Honestly, BTRFS is wonderful to work with. It replaced me using mergerfs with snapraid a while ago.

  • A real-time switch would eliminate the need for a custom-built kernel for low-latency operations such as music recording and CNC. Distros that use these are often running older kernels, creating security issues, as well, as missing features found in fresh kernels. If it low-latency operation were just a switch, no custom compiling would need to be done.
    • by wed128 ( 722152 )

      It's really not that simple from an implementation perspective. Linux is rather inappropriate as an RTOS; it was very much designed for throughput over latency. If RT performance is really important, i'd choose another OS such as VxWorks or QNX.

Think of it! With VLSI we can pack 100 ENIACs in 1 sq. cm.!

Working...