On-demand reaping of the MRU cache
Instead of running the mru cache reaper all the time based on a
timeout, we should only run it when the cache has active objects.
This allows CPUs to sleep when there is no activity rather than
be woken repeatedly just to check if there is anything to do.
Date: Thu Aug 2 17:24:38 AEST 2007
Workarea: chook.melbourne.sgi.com:/build/dgc/isms/2.6.x-xfs
Inspected by: donaldd
The following file(s) were checked into:
longdrop.melbourne.sgi.com:/isms/linux/2.6.x-xfs-melb
Modid: xfs-linux-melb:xfs-kern:29305a
fs/xfs/xfs_mru_cache.h - 1.2 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_mru_cache.h.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h
- Change the reaper to start when the first object is stored
in the cache and stop when the last object is reaped.
fs/xfs/xfs_mru_cache.c - 1.2 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_mru_cache.c.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h
- Change the reaper to start when the first object is stored
in the cache and stop when the last object is reaped.
fs/xfs/xfs_filestream.c - 1.2 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_filestream.c.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h
- No longer need to tell the MRU cache to restart the reaper
when we flush the cache.
|