> What are your plans? If you've not decided, here is space-saving
> suggestion for the inode:
>
> struct ext2_inode {
[snip]
> __u32 i_size; /* Size in bytes */
> __u32 i_atime; /* Access time */
> __u32 i_ctime; /* inode Change time */
> __u32 i_mtime; /* Modification time */
> __u32 i_dtime; /* Deletion Time */
after 2038, we'll need larger time.
> __u32 i_blocks; /* Blocks count */
The number of blocks needs to be higher when we have
64-bit sized files.
> union {
> __u32 i_dir_acl; /* Directory ACL (directories only) */
> __u32 i_size_high; /* high 32 bits of 64-bit size */
> } u2;
Looks good. Considering how well ext2 scales with large
directories, we don't really wand >2G directories :-)
Rik.
+-----------------------------+------------------------------+
| For Linux mm-patches, go to | "I'm busy managing memory.." |
| my homepage (via LinuxHQ). | H.H.vanRiel@fys.ruu.nl |
| ...submissions welcome... | http://www.fys.ruu.nl/~riel/ |
+-----------------------------+------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu