#linux616 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #linux616, aggregated by home.social.
-
#Linux :tux: 6.16: Entspannt zu mehr Leistung | heise online https://www.heise.de/news/Linux-6-16-Entspannt-zu-mehr-Leistung-10503711.html #Linux616 #OpenSource
-
💡 Kernel Linux 6.16-rc3 porta miglioramenti driver e stabilità
https://gomoot.com/kernel-linux-6-16-rc3-porta-miglioramenti-driver-e-stabilita/
-
💡 Kernel Linux 6.16-rc3 porta miglioramenti driver e stabilità
https://gomoot.com/kernel-linux-6-16-rc3-porta-miglioramenti-driver-e-stabilita/
-
💡 Kernel Linux 6.16-rc3 porta miglioramenti driver e stabilità
https://gomoot.com/kernel-linux-6-16-rc3-porta-miglioramenti-driver-e-stabilita/
-
Linux 6.16 yields improved EXT4 performance!
As part of the changes that are done in Linux 6.16, there are some of the very interesting changes that are done to the EXT4 filesystem. Those changes yield improved performance, causing you to have a faster EXT4 filesystem compared to the recently released Linux 6.15.
Those changes have been made to improve the filesystem performance, which will be pushed to the v6.16 development branch from this PR, including:
- Fast commit performance improvements
- Multi-fsblock atomic write support for bigalloc file systems
- Large folio support for regular files
The large folio support for regular files was, in itself, a factor of the improvements, along with all other changes, which yielded over 37% performance increase according to the kernel test robot that made this report you can see here. According to the test robot, it has reported that it had noticed a 37.7% improvement on
fsmark.files_per_sec.The large folio support for regular files has been added with this patch, which checks for the following conditions in the
ext4_should_enable_large_folio()function before enabling such support:- If
i_modeon an inode is a regular file using theS_ISREG()macro - If either the data flags on the superblock or the inode flags has the journal data flags
- If the superblock has no verity and has no encryption support
Also, Linux 6.16 fixes some corruption bugs on an EXT4 file system caused by race conditions in the extent status tree. Those race conditions were potentially manifested from the heavy simultaneous allocation and deallocation to a single file.
Expect the first release candidate of Linux 6.16 in the next two weeks!
#EXT4 #Filesystem #Linux #Linux616 #LinuxKernel #news #Tech #Technology #update
-
A document describes techniques that are useful for debugging suspend and resume issues with modern #AMD processors was merged for #Linux 6.16: https://git.kernel.org/torvalds/c/cafb22242bfb7fad10fde6f9b99853fc924e691a
Rendered version: https://origin.kernel.org/doc/html/next/arch/x86/amd-debugging.html
-
Support task local hash maps[1], FUTEX2_NUMA[2], and FUTEX2_MPOL[3] was merged for #Linux 6.16:
https://git.kernel.org/torvalds/c/b3570b00dc3062c5a5e8d9602b923618d679636a
See also: https://lore.kernel.org/all/2025041616[email protected]/
[1] https://git.kernel.org/torvalds/c/80367ad01d93ac781b0e1df246edaf006928002f
[2] https://git.kernel.org/torvalds/c/cec199c5e39bde7191a08087cc3d002ccfab31ff
[3] https://git.kernel.org/torvalds/c/c042c505210dc3453f378df432c10fff3d471bc5
-
A option to optimize the code for the local CPU was merged for #Linux 6.16:
https://git.kernel.org/torvalds/c/ea1dcca1de129dfdf145338a868648bc0e24717c
To quote: '"Add a 'native' option that allows users to build an optimized kernel for their local machine (i.e. the machine which is used to build the kernel) by passing '-march=native' to CFLAGS.
The idea comes from Linus' reply to Arnd's initial proposal:
https://lore.kernel.org/all/CAHk-=wji1[email protected]/
Here are some numbers comparing 'generic' to 'native' on a Skylake dual-core laptop (generic --> native) […]
There is little difference both in terms of size and of performance, however
the native build comes out on top ever so slightly [3 % in some cases]."'Note, the author tried in on a different machine later, and there it made no real difference:
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #XFS merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/f83fcb87f824b0bfbf1200590cc80f05e66488a7):
- Atomic writes for XFS
- Remove experimental warnings for pNFS, scrub and parent pointers
-
Highlights from the main #bcachefs merge for #Linux 6.16: https://git.kernel.org/torvalds/c/522544fc71c27b4b432386c7919f71ecc79a3bfb
- Incompatible features may now be enabled at runtime, via "opts/version_upgrade" in sysfs.
- Various changes to support deployable disk images
- Major error message improvements for btree node reads, data reads, and elsewhere.
- New option, 'rebalance_on_ac_only'.
- Repair/self healing:
- We can now kick off recovery passes and run them in the background if we detect errors.
- Performance:
- Faster snapshot deletion
- Faster device removal
- We're now coalescing redundant accounting updates prior to transaction commit, taking some pressure off the journal.
- Stack usage improvements: All allocator state has been moved off the stack -
"some performance improvements and one minor mount option update" are among the main #Btrfs changes merged for #Linux 6.16:
https://git.kernel.org/torvalds/c/5e82ed5ca4b510e0ff53af1e12e94e6aa1fe5a93
A few highlights:
Performance:
- extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime)
- extent io tree cleanups lead to performance improvements by avoiding unnecessary searches or repeated searches
- more efficient extent unpinning when committing transaction (estimated run time improvement 3-5%)
User visible changes:
- remove standalone mount option 'nologreplay', deprecated in 5.9, replacement is 'rescue=nologreplay'
- in scrub, update reporting, add back device stats message after detected errors (accidentally removed during recent refactoring)
Core:
- convert extent buffer radix tree to xarray
- continued preparations for large folios