From 5ec70b73d772fa9a70936e6208cf60bf636b3fba Mon Sep 17 00:00:00 2001 From: Dave Chinner Date: Fri, 8 Jul 2011 14:14:45 +1000 Subject: [PATCH] --- yaml --- r: 257371 b: refs/heads/master c: 8ab47664d51a69ea79fe70bb07ca80664f74f76b h: refs/heads/master i: 257369: 2b2733c492c4a97f7e2133189ff286fd2593fa3b 257367: 0a62310511165d4c25594badc4c9757a43bd93dd v: v3 --- [refs] | 2 +- trunk/Documentation/filesystems/vfs.txt | 6 ++++++ trunk/fs/super.c | 1 + 3 files changed, 8 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index 38ced3ad875d..c1e172b4ab85 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 0e1fdafd93980eac62e778798549ce0f6073905c +refs/heads/master: 8ab47664d51a69ea79fe70bb07ca80664f74f76b diff --git a/trunk/Documentation/filesystems/vfs.txt b/trunk/Documentation/filesystems/vfs.txt index fd24f34f120f..6bf85b78cfea 100644 --- a/trunk/Documentation/filesystems/vfs.txt +++ b/trunk/Documentation/filesystems/vfs.txt @@ -317,6 +317,12 @@ or bottom half). the VM is trying to reclaim under GFP_NOFS conditions, hence this method does not need to handle that situation itself. + Implementations must include conditional reschedule calls inside any + scanning loop that is done. This allows the VFS to determine + appropriate scan batch sizes without having to worry about whether + implementations will cause holdoff problems due to large scan batch + sizes. + Whoever sets up the inode is responsible for filling in the "i_op" field. This is a pointer to a "struct inode_operations" which describes the methods that can be performed on individual inodes. diff --git a/trunk/fs/super.c b/trunk/fs/super.c index 5101f0544960..7943f04cb3a9 100644 --- a/trunk/fs/super.c +++ b/trunk/fs/super.c @@ -182,6 +182,7 @@ static struct super_block *alloc_super(struct file_system_type *type) s->s_shrink.seeks = DEFAULT_SEEKS; s->s_shrink.shrink = prune_super; + s->s_shrink.batch = 1024; } out: return s;