| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: [Patch] unique per-AG inode generation number initialisation |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 7 Apr 2008 08:57:38 -0400 |
| Cc: | xfs-dev <xfs-dev@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <20080401231815.GW103491721@sgi.com> |
| References: | <20080401231815.GW103491721@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
I don't really like this. The chance to hit a previously used generation seems to high. What about making the first few bits of each generation number a per-ag counter that's incremented anytime we deallocate an inode cluster? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Patch] fix lock inversion in forced unmount, Christoph Hellwig |
|---|---|
| Next by Date: | performance problems with XFS and Linux kernel 2.6.24.4, Bond Masuda |
| Previous by Thread: | Re: [Patch] unique per-AG inode generation number initialisation, Hans-Peter Jansen |
| Next by Thread: | Re: [Patch] unique per-AG inode generation number initialisation, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |