Enhance vfs_aio_ratelimit with configurable burst support, persistent rate state, and improved bandwidth configuration. The enhancement should introduce: - Configurable burst allowance for read and write operations. - Persistent rate-limiter state per share to ensure consistent enforcement across restarts. - Support for human-readable bandwidth values (e.g., 1M, 500K, 2G) while maintaining backward compatibility.
4.24 is rc state already; feature enhancements will go to master and be part of the next stable release in 6 months.
This bug was referenced in samba master: f6a67c361bcb0d9f4a7f451dcfda800775b5be13 306612e09c082282f39789c426ea85cc7e2bb6e3 d6332b2caf03e4fcbed0a67208251a27601c527d 9b54d8beaefd9b835b971dd0370d3a1f198121d8 83f4b51175cdaa20039de7e823bc4c6a15893628
Created attachment 18874 [details] patch from master for v4-24-test
(In reply to Björn Jacke from comment #1) Björn, this module just got introduced within the 4.24.0 rc cycle and we had to still change some smb.conf config parameters and fix some of the inner workings of that module to make it properly work. I believe in that case we should really avoid creating a painful config incompatibility while we still can resolve it prior to the 4.24.0 final release. I agree that other upcoming major enhancements (e.g. clustering support) for that module need to go into the next release branch.
Re-assigning for 4.24 inclusion.
(In reply to Guenther Deschner from comment #4) okay, in this case let's add it to the release branch. In genereal this should be avoided though. Functionallity-wise unfinished modules will then be part of the next release 6 months later.
This bug was referenced in samba v4-24-test: 5abe6ef48b8e723ffbdae8209b5a551a7d98281c c025dfa0352a504259077523d833f731692c2a26 50865f5d7e5ef597229aa45c9e378158dbcb031f e323eb43897f3eb8d5d3678ba2de90a004ed7b2c 417ddbe6c990c27ec024fcdbdadd9ddb9d70315e
This bug was referenced in samba v4-24-stable (Release samba-4.24.0): 5abe6ef48b8e723ffbdae8209b5a551a7d98281c c025dfa0352a504259077523d833f731692c2a26 50865f5d7e5ef597229aa45c9e378158dbcb031f e323eb43897f3eb8d5d3678ba2de90a004ed7b2c 417ddbe6c990c27ec024fcdbdadd9ddb9d70315e