Re: [PATCH 0/4] Use 64-bit inode numbers internally in the kernel

On 8/14/06, David Howells <[email protected]> wrote:


These patches make the kernel use 64-bit inode numbers internally, even on a
32-bit system.  They are required because some filesystems have intrinsic
64-bit inode numbers: NFS and XFS for example.  The 64-bit inode numbers are
then propagated to userspace automatically where the arch supports it.


Out of curiosity, is there a performance hit for 32-bit systems?  Have
you done any minimal benchmarks to see?

josh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 0/4] Use 64-bit inode numbers internally in the kernel
  - From: David Howells <[email protected]>

Prev by Date: Re: [PATCH 1/2] acpi,backlight: MSI S270 laptop support - ec_transaction()
Next by Date: [2.6 patch] orinoco.h: "extern inline" -> "static __always_inline"
Previous by thread: [RHEL5 PATCH 3/4] VFS: Clear up u-long-long ino_t print format warnings
Next by thread: Re: [PATCH 0/4] Use 64-bit inode numbers internally in the kernel
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]