This is because Linux does synchronous metadata updates on
unlink(). And even when it doesn't do that, it will still
need to do synchronous metadata _reads_ in order to determine
what to write out asynchronously.
> Is it possible to optimize this?
Well, we could recode the kernel to let bdflush or a new
kernel daemon do the unlinks... Apart from that, there's
not much of a solution :(
(or you simply run 'rm -rf dir &', which will probably
be the same thing that Solaris does internaly :-)
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