On Fri, Jun 21, 2024 at 10:09:07AM +0700, Konst Mayer wrote: > Hi Darrick, > > Thanks for the patch. Is there a reason why it is not in the mainline yet? Lack of review bandwidth, I'm sorry to say. --D > Best regards, > Konst > > "Darrick J. Wong" <djwong@xxxxxxxxxx> wrote: > > Hi all, > > > > One thing that's been missing for a long time is the ability to tell > > underlying storage that it can unmap the unused space on the realtime > > device. This short series exposes this functionality through FITRIM. > > Callers that want ranged FITRIM should be aware that the realtime space > > exists in the offset range after the data device. However, it is > > anticipated that most callers pass in offset=0 len=-1ULL and will not > > notice or care. > > > > If you're going to start using this code, I strongly recommend pulling > > from my git trees, which are linked below. > > > > This has been running on the djcloud for months with no problems. Enjoy! > > Comments and questions are, as always, welcome. > > > > --D > > > > kernel git tree: > > https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=realtime-discard > > > > fstests git tree: > > https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=realtime-discard > > --- > > Commits in this patchset: > > * xfs: enable FITRIM on the realtime device > > --- > > fs/xfs/xfs_discard.c | 252 +++++++++++++++++++++++++++++++++++++++++++++++++- > > fs/xfs/xfs_trace.h | 29 ++++++ > > 2 files changed, 274 insertions(+), 7 deletions(-) > > >
