>>>>> " " == Andi Kleen <[EMAIL PROTECTED]> writes: > Steal a couple of bytes from what ? >From the 32-bit storage area currently allocated to i_generation on the on-disk ext2fs inode (as per Ted's suggestion). With current disk/computing speeds, you probably don't need the full 32 bits to offer a reasonable guarantee of inode number uniqueness. Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: NFS locking bug -- limited... Rogier Wolff
- Re: NFS locking bug -- limited... Theodore Y. Ts'o
- Re: NFS locking bug -- limited... Andreas Dilger
- Re: NFS locking bug -- limited... Albert D. Cahalan
- Re: NFS locking bug -- limited mtime re... Theodore Y. Ts'o
- Re: NFS locking bug -- limited mti... Andi Kleen
- Re: NFS locking bug -- limited... Trond Myklebust
- Re: NFS locking bug -- limited... Theodore Y. Ts'o
- Re: NFS locking bug -- limited... Trond Myklebust
- Re: NFS locking bug -- limited... Andi Kleen
- Re: NFS locking bug -- limited... Trond Myklebust
- Re: NFS locking bug -- limited mtime resolution mea... Trond Myklebust
- Re: NFS locking bug -- limited mtime resolution... Michael Eisler
- Re: NFS locking bug -- limited mtime resolu... Jeff Epler
- Re: NFS locking bug -- limited mtime resolu... Trond Myklebust
- Re: NFS locking bug -- limited mtime resolution means nf... James Yarbrough
- Re: NFS locking bug -- limited mtime resolution mea... Trond Myklebust
- Re: NFS locking bug -- limited mtime resolution... Michael Eisler
- Re: NFS locking bug -- limited mtime resolu... Trond Myklebust
- Re: NFS locking bug -- limited mtime re... Michael Eisler
- Re: NFS locking bug -- limited mti... Trond Myklebust