>> But we have to make _some_ decision about it at boot time. The cost
>> of having it too large on a less file-intensive workload may be less
>> than the cost of having it too small if you really are using that many
>> inodes.
>
>At the point its cache footprint becomes significant then it ceases to be
>a further win surely ?
That havn't anything to do with cache, it's only a complexity math
problem.
Andrea
-
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.tux.org/lkml/