| To: | Richard Ems <richard.ems@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS unlink still slow on 3.1.9 kernel ? |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 14 Feb 2012 14:07:53 -0500 |
| Cc: | Jeffrey Hundstad <jeffrey.hundstad@xxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <4F3AA40D.50302@xxxxxxxxxxxxxxxxx> |
| References: | <4F3A5B49.6020803@xxxxxxxxxxxxxxxxx> <4F3AA191.9030606@xxxxxxxx> <4F3AA40D.50302@xxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Tue, Feb 14, 2012 at 07:12:29PM +0100, Richard Ems wrote: > # /net/c3m/usr/local/software/XFS/summarise_stat.pl /bin/ > 9 6.2% are scripts (shell, perl, whatever) > 65 44.8% don't use any stat() family calls at all > 61 42.1% use 32-bit stat() family interfaces only > 9 6.2% use 64-bit stat64() family interfaces only > 1 0.7% use both 32-bit and 64-bit stat() family interfaces > > So I was not sure if I should use inode64 or not. Are you on a 32-bit system (userspace, kernel doesn't matter)? If the system is 64-bit even the plain stat handles 64-bit inodes just fine. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | xfs_fsr (defragmenting) 'XFS_IOC_SWAPEXT failed: ino=xxxxxx: Invalid argument' error, Tom Crane |
|---|---|
| Next by Date: | Re: XFS unlink still slow on 3.1.9 kernel ?, Christoph Hellwig |
| Previous by Thread: | Re: XFS unlink still slow on 3.1.9 kernel ?, Richard Ems |
| Next by Thread: | Re: XFS unlink still slow on 3.1.9 kernel ?, Richard Ems |
| Indexes: | [Date] [Thread] [Top] [All Lists] |