> You might want to pay particular attention to the allocation and
> freeing of *inodes* (and, to a lesser extent, dentries) as they
> concern performance on low-memory machines. Since not long after
> Linus first rewrote "fs/inode.c" in the 2.1.xx tree (around the
> 2.1.50s), I've been using a patch which frees inodes much more
> aggressively than the stock kernel does when memory gets tight, and
> I've had much better luck with it on small-memory machines.
>
> semi-permanent data structures). With maybe as many as 1 in 5 pages
> dedicated to inodes, we should not be surprised to encounter some poor
> performance and serious fragmentation now and then.
Yay, this is the way to go... The *inode* cache might indeed
be the biggest problem the current kernel has wrt. fragmentation.
How stupid of me to overlook this item (and not include it
in the MM todo list)...
I'll check out the patch and see if we can improve it!
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu