Message ID | 164325106958.29787.4865219843242892726.stgit@noble.brown (mailing list archive) |
---|---|
Headers | show |
Series | Remove remaining parts of congestions tracking code. | expand |
On Thu, 27 Jan 2022 13:46:29 +1100 NeilBrown <neilb@suse.de> wrote: > Congestion hasn't been reliably tracked for quite some time. > Most MM uses of it for guiding writeback decisions were removed in 5.16. > Some other uses were removed in 17-rc1. > > This series removes the remaining places that test for congestion, and > the few places which still set it. > > The second patch touches a few filesystems. I didn't think there was > much value in splitting this out by filesystems, but if maintainers > would rather I did that, I will. > > The f2fs, cephfs, fuse, NFS, and block patches can go through the > respective trees proving the final patch doesn't land until after they > all do - so maybe it should be held for 5.18-rc2 if all the rest lands > by 5.18-rc1. Plan B: I'll just take everything. While collecting tested-bys and acked-bys from filesystem maintainers (please).
On 1/26/22 7:46 PM, NeilBrown wrote: > Congestion hasn't been reliably tracked for quite some time. > Most MM uses of it for guiding writeback decisions were removed in 5.16. > Some other uses were removed in 17-rc1. > > This series removes the remaining places that test for congestion, and > the few places which still set it. > > The second patch touches a few filesystems. I didn't think there was > much value in splitting this out by filesystems, but if maintainers > would rather I did that, I will. > > The f2fs, cephfs, fuse, NFS, and block patches can go through the > respective trees proving the final patch doesn't land until after they > all do - so maybe it should be held for 5.18-rc2 if all the rest lands > by 5.18-rc1. For the series: Acked-by: Jens Axboe <axboe@kernel.dk>