Use less cache for the hash table overall.
Use less lowmem.
Ideally there would be no tradeoff if you can still get reasonable
hash chain length with smaller tables (= overall win)
>
> I take it you're happy enough with the current hash function distribution?
At least I don't know how to improve it.
> > Also same for inode hash (but I don't have statistics for that right now)
>
> I could hack something up ... but 1 machine ain't going to cut it. I
> suspect I'd have a much smaller inode hash, as I tend to have masses
> of kernel trees, mostly hardlinked to each other.
I doubt inode cache is very critical, except perhaps in NFS server loads
(but even the nfs server has an own frontend cache)
Normally the dcache should bear most of the load.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/