Re: [PATCH 06/11] xfs: deferred inode inactivation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 06/11] xfs: deferred inode inactivation
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 16 Mar 2021 07:27:10 +0000
Cc: linux-xfs@xxxxxxxxxxxxxxx
In-reply-to: <161543197372.1947934.1230576164438094965.stgit@magnolia>
References: <161543194009.1947934.9910987247994410125.stgit@magnolia> <161543197372.1947934.1230576164438094965.stgit@magnolia>

Still digesting this.  What trips me off a bit is the huge amount of
duplication vs the inode reclaim mechanism.  Did you look into sharing
more code there and if yes what speaks against that?

Follow-Ups:
- Re: [PATCH 06/11] xfs: deferred inode inactivation
  - From: Darrick J. Wong

References:
- [PATCHSET v3 00/11] xfs: deferred inode inactivation
  - From: Darrick J. Wong
- [PATCH 06/11] xfs: deferred inode inactivation
  - From: Darrick J. Wong

Prev by Date: Re: [PATCH 45/45] xfs: expanding delayed logging design with background material
Next by Date: Re: [PATCH 01/45] xfs: initialise attr fork on inode create
Previous by thread: [PATCH 06/11] xfs: deferred inode inactivation
Next by thread: Re: [PATCH 06/11] xfs: deferred inode inactivation
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux