| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] XFS: remove i_gen from incore inode |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Mon, 21 Jul 2008 21:08:14 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20080721075449.GB6692@xxxxxxxxxxxxx> |
| Mail-followup-to: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| References: | <1216558002-838-1-git-send-email-david@xxxxxxxxxxxxx> <20080721075449.GB6692@xxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Mon, Jul 21, 2008 at 03:54:49AM -0400, Christoph Hellwig wrote: > On Sun, Jul 20, 2008 at 10:46:42PM +1000, Dave Chinner wrote: > > i_gen is incremented in directory operations when the > > directory is changed. It is never read or otherwise used > > so it should be removed to help reduce the size of the > > struct xfs_inode. > > It also removes a xfs_trans_log_inode in xfs_remove, which looks > fine to me from a quick glance, but this should be verified and > documented. If you note in the very next if/else statement the directory inode gets logged - either by dropping the link or directly. IOWs, we were logging the directory inode twice with the same value (XFS_ILOG_CORE). So I don't think thereśs any problem here. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] XFS: Use KM_NOFS for incore inode extent tree allocation V2, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH 1/4] XFS: Remove xfs_iflush_all and clean up xfs_finish_reclaim_all(), Dave Chinner |
| Previous by Thread: | Re: [PATCH] XFS: remove i_gen from incore inode, Christoph Hellwig |
| Next by Thread: | Re: [PATCH] XFS: remove i_gen from incore inode, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |