[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lustre-devel
Subject:    [Lustre-devel] SOM re-design, overview
From:       Alex.Zhuravlev () Sun ! COM (Alex Zhuravlev)
Date:       2010-02-03 17:05:15
Message-ID: 4B69ACCB.4020006 () sun ! com
[Download RAW message or body]

On 2/3/10 7:46 PM, Vitaly Fertman wrote:
> I. Introduction.
>
> SOM is split to several simple mechanisms: invalidation, revalidation,
> llog cleanup.

for ones who are new with SOM (Size on MDS):

SOM attributes - i_size, i_blocks and i_atime of a file, currently we
take them from OST (meaning a bunch of RPCs, and 2 * RTT at least)

in order to improve some workloads (like ls -l) we'd like to cache SOM
attributes so that getattr can be done in RTT with 1 RPC.

revalidation - a process to cache SOM attributes on MDS. we can do
revalidation when file isn't open for write and all cached (dirty)
data is written.

invalidation - a process to drop cached SOM attributes on MDS. 
invalidation starts when file is open for write. from this point to
successful revalidation SOM attributes can't be cached on MDS and
instead should be taken from OST (as we do currently).


z.


[prev in list] [next in list] [prev in thread] [next in thread]