Tomasz Torcz wrote:
On Fri, Jun 09, 2006 at 07:50:08PM -0400, Theodore Ts'o wrote:
So without further ado, here are some ideas of ways that we can slim
down struct inode:
1) Move i_blksize (optimal size for I/O, reported by the stat system
call). Is there any reason why this needs to be per-inode, instead
of per-filesystem?
2) Move i_blkbits (blocksize for doing direct I/O in bits) to struct
super. Again, why is this per-inode?
ZFS filesystem uses dynamic, per-file blocksizes. Some Linux
filesystem may implement something like this in order to be called
"modern".
Yep, Sun stole my buckets idea <j/k> I think ZFS calls them
"meta-slabs" or somesuch.
See what I posted in the 'continuous inodes' sub-thread.
Jeff
-
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/
[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]
