linux.git/fs/9p/cache.h, branch v4.0

9p: make v9fs_cache_inode_{get,put,set}_cookie empty inlines for !9P_CACHEFS

2013-10-25T03:34:47+00:00

Signed-off-by: Al Viro

fs/9p: When doing inode lookup compare qid details and inode mode bits.

2011-07-23T14:32:48+00:00

This make sure we don't use wrong inode from the inode hash. The inode number
of the file deleted is reused by the next file system object created
and if we only use inode number for inode hash lookup we could end up
with wrong struct inode.

Also compare inode generation number. Not all Linux file system provide
st_gen in userspace. So it could be 0;

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Eric Van Hensbergen

fs/9p: Add v9fs_inode

2011-03-15T14:57:39+00:00

Switch to the fscache code to v9fs_inode. We will later use
v9fs_inode in cache=loose mode to track the inode cache
validity timeout. Ie if we find an inode in cache older
that a specific jiffie range we will consider it stale

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen

fs/9p: [fscache] wait for page write in cached mode

2011-03-15T14:57:37+00:00

We need to call fscache_wait_on_page_write in launder_page
for fscache

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen

9p: Add fscache support to 9p

2009-09-23T18:03:46+00:00

This patch adds a persistent, read-only caching facility for
9p clients using the FS-Cache caching backend.

When the fscache facility is enabled, each inode is associated
with a corresponding vcookie which is an index into the FS-Cache
indexing tree. The FS-Cache indexing tree is indexed at 3 levels:
- session object associated with each mount.
- inode/vcookie
- actual data (pages)

A cache tag is chosen randomly for each session. These tags can
be read off /sys/fs/9p/caches and can be passed as a mount-time
parameter to re-attach to the specified caching session.

Signed-off-by: Abhishek Kulkarni 
Signed-off-by: Eric Van Hensbergen