On Thu, 2016-06-23 at 17:38 +0100, Pádraig Brady wrote: > > I'm thinking this logic shouldn't be within du.
I can't see how it couldn't/wouldn't be. > Perhaps a wrapper that reads such cached values if available would be > better. And then does what? Gives them to du to see it's tally of the dirs/subdirs? > Something more general that I mentioned before in the context of file > checksums, > would be to have extended attributes that were auto cleared on write > by the system, where one could cache checksums and sizes etc. How does that avoid du from having to trawl the entire tree every time? I think you are just splitting hairs on whether du gets information from directory metadata or EAs. I'm trying to avoid descending into a directory tree entirely by caching the results of the last descent into it at the top of it. Cheers, b.
signature.asc
Description: This is a digitally signed message part
