It's possible to increase inodes one page past the inode-max limit.
> As second is there a way to avoid the use of so many inodes in 2.1.x
> kernels? And why 2.1.x leave so many inode used?
>
> So many inode allocated should help a lot to make not happy low memory
> machines (I think this is the first cause of the find />/dev/null
> slowdown at second launch on 2.1.x with little ram)...
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);
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.
Regards,
Bill
-
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