Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

Started by Nikolai Joukov on Dec 25, 2006

open the first message on its own page

Message details and related content
quoted
Every stackable file system caches the data at its own level and
copies it from/to the lower file system's cached pages when necessary.
...
this effectively reduces the system's cache memory size by two or more
times.
It should not be that bad with a decent cache replacement policy; I
wonder if observing the problem (that you corrected in the various ways
you've described), you got some insight as to what exactly was happening.
I agree that appropriate replacement policies can partially eliminate
the double caching problem for stackable file systems.  In fact, that's
exactly what RAIF does: it forces the data pages of the lower file
systems to be evicted right after they are written and are not needed
anymore.  This solves the problem for most write-intensive workloads.
Without this optimization the situation is much worse because Linux is
trying to protect caches of different file systems from each other.  But,
as you mentioned, any cache replacement policy is optimized for some set
of workloads and is bad for some other set of workloads.  Also, caching
the data at multiple layers not just increases the memory consumption but
also adds CPU time overheads because of the data copying between the
pages.  I believe that the real solution to the problem is the ability to
share data pages between file systems.

Nikolai.
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help