In order to mitigate potential issues related to journal credit usage, the folio writeback process can be configured to allocate credits for only one extent at a time. However, the current tracepoints do not fully capture the writeback position or the return values during the submission of folios, which could lead to challenges when handling large and non-contiguous folios that demand a significant amount of journal credits. The ext4_write_extent() function, responsible for writing back these large folios, has also been updated to address these concerns and is now available in the ext4_write_extent() package.
For those interested in accessing Linux kernel 6.16.3, the full source code, patch, and PGP signature can be found at the provided links:
- Full source: [Download here](https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.16.3.tar.xz)
- Patch: [Download here](https://cdn.kernel.org/pub/linux/kernel/v6.x/patch-6.16.3.xz)
- PGP Signature: [Download here](https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.16.3.tar.sign)
Additionally, a summary of all the changes made in this release can be viewed at this URL: [View changes](https://git.kernel.org/stable/ds/v6.16.3/v6.16.2).
As the Linux kernel continues to evolve, future updates are expected to introduce additional enhancements and optimizations, further enhancing performance and stability across various systems. Users and developers alike are encouraged to stay informed about these developments and consider upgrading to benefit from the latest features and improvements
Linux Kernel 6.16.3 released
Linux kernel 6.16.3 has been released. The Linux kernel has been enhanced to accommodate large folios, facilitating more efficient processing of extents. The semantics of reserving credits in pages are now obsolete; instead, credits are reserved in extents. The folio writeback process has the capability to either extend journal credits or initiate a new transaction in the event that the currently reserved journal credits are inadequate. To tackle this issue, the folio writeback process can be adjusted to allocate credits for only one extent initially. The current tracepoints do not adequately capture the writeback position and the return value prior to and following the submission of the folios. Submitting a sufficiently large and discontinuous folio may utilize a substantial amount of journal credits, thereby imposing considerable pressure on the journal. The ext4_write_extent() function, which writes back a large and non-contiguous folio, may also encounter this issue. The ext4_write_extent() function has been updated and is now accessible in the ext4_write_extent() package.
