| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 4/5] xfs: remove m_litino |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sat, 21 Mar 2009 16:09:14 -0400 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <49C465AC.3010809@xxxxxxxxxxx> |
| References: | <20090318094119.561416000@xxxxxxxxxxxxxxxxxxxxxx> <20090318094132.224487000@xxxxxxxxxxxxxxxxxxxxxx> <49C465AC.3010809@xxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Fri, Mar 20, 2009 at 10:57:32PM -0500, Eric Sandeen wrote: > Christoph Hellwig wrote: > > > With the upcoming v3 inodes the inode data/attr area size needs to be > > calculated for each specific inode, so we can't cache it in the superblock > > anymore. > > hm, ok, but why do this now? It could be considered a cleanup as there's no point in caching a constant expression in the superblock. More importantly I want to get as many of the CRC preparation patches upstream so that I don't have to keep rebasing them. |
| Previous by Date: | Re: [PATCH 3/5] xfs: kill ino64 mount option, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH] xfstests: add test 203, xfs_io bmap reallocation, Eric Sandeen |
| Previous by Thread: | Re: [PATCH 4/5] xfs: remove m_litino, Eric Sandeen |
| Next by Thread: | Re: [PATCH 4/5] xfs: remove m_litino, Felix Blyakher |
| Indexes: | [Date] [Thread] [Top] [All Lists] |