>I think the kernel would be better off with an inode limit that scaled
>with memory size. Using a simple value like
>
> max_inodes = (num_physpages >> 1);
Yes, but in 2.0.x max_inodes is never reached.
>would probably work well over a wide range of systems. The current
>default of 4096 is too big for anything much under 32M. You might want
>to experiment with different limits.
The point is "why 2.1.x alloc so many inodes while 2.0.x not?". In 2.0.x
the max_inodes is set to 3072 but after a "find /" I get only 400 inode
allocated while 2.1.x always allocate more inodes than the max_inodes.
In 2.1.110-pre2 after a "find /" with 32Mbyte:
root@ark:/proc/sys/fs# cat inode-max
300
root@ark:/proc/sys/fs# cat inode-nr
1232 7
While in 2.0.x inode-max was 30xx and inode-nr was 300 or so on...
Andrea[s] Arcangeli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html