Re: [RFC] Per-inode metadata cache.

Stephen C. Tweedie (sct@redhat.com)
Tue, 19 Oct 1999 11:51:04 +0100 (BST)


Hi,

On 19 Oct 1999 00:44:38 -0500, ebiederm+eric@ccr.net (Eric
W. Biederman) said:

> Meanwhile having the metadata in the page cache (where they would
> have predictable offsets by file size)

Doesn't help --- you still need to look up the physical block numbers
in order to clear the allocation bitmaps for indirect blocks, so we're
going to need those lookups anyway. Once you have that, looking for a
given fixed offset in the buffer cache is no harder than doing so in
the page cache.

> would also speed handle partial truncates . . . [ Either case with
> a little gentle handling will handle speed up fsync] (At least for
> ext2 type filesystems).

No argument there, but a per-inode dirty buffer list would do the
same. Neither of these are overwhelming arguments for a move.

--Stephen

-
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/