Documentation/filesystems/unionfs/usage.txt | 39 +++++++++++++++++++-------
fs/drop_caches.c | 4 +--
fs/unionfs/dentry.c | 11 +++++++
fs/unionfs/super.c | 34 ++++++++---------------
fs/unionfs/union.h | 1 +
include/linux/mm.h | 2 -
6 files changed, 53 insertions(+), 38 deletions(-)
New commits:
commit 3443ab22a746c5eaa8c1be543b3e155f4876a7fb
Author: Erez Zadok <[EMAIL PROTECTED]>
Date: Thu Dec 13 17:17:49 2007 -0500
Unionfs: clarify usage.txt mount options
CC: Jim Kissel <[EMAIL PROTECTED]>
Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>
commit a038eb5a4f1db9430b434f0785f0114714fdafc4
Author: Erez Zadok <[EMAIL PROTECTED]>
Date: Thu Dec 13 10:51:15 2007 -0500
Unionfs: avoid using drop_pagecache_sb in remount
Exporting drop_pagecache_sb to modules is somewhat risky because one cannot
sleep inside invalidate_mapping_pages. This could cause a lot of latency in
the pre-emption code. So don't export this symbol to minimize the risk that
others will use it.
Instead, unionfs will try to directly invalidate as many pages it can from
the unionfs_remount code. Invalidating those inode pages is not strictly
required, but helpful in encouraging a revalidation of inodes sooner than
waiting for individual f/s ops to access the union. Since a remount is
already an expensive but rare operation, this inode pages invalidation
shouldn't add too much overhead.
CC: Nick Piggin <[EMAIL PROTECTED]>
Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>
_______________________________________________
unionfs-cvs mailing list: http://unionfs.filesystems.org/
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs-cvs
