[PATCH 40/43] fscache: drop references to slow-work

From: Tejun Heo
Date: Fri Feb 26 2010 - 07:15:21 EST


fscache no longer uses slow-work. Drop references to it.

NOT_SIGNED_OFF_YET
Cc: David Howells <dhowells@xxxxxxxxxx>
---
fs/fscache/Kconfig | 1 -
fs/fscache/main.c | 7 -------
include/linux/fscache-cache.h | 1 -
3 files changed, 0 insertions(+), 9 deletions(-)

diff --git a/fs/fscache/Kconfig b/fs/fscache/Kconfig
index 864dac2..526245a 100644
--- a/fs/fscache/Kconfig
+++ b/fs/fscache/Kconfig
@@ -2,7 +2,6 @@
config FSCACHE
tristate "General filesystem local caching manager"
depends on EXPERIMENTAL
- select SLOW_WORK
help
This option enables a generic filesystem caching manager that can be
used by various network and other filesystems to cache data locally.
diff --git a/fs/fscache/main.c b/fs/fscache/main.c
index 9250470..7404b0e 100644
--- a/fs/fscache/main.c
+++ b/fs/fscache/main.c
@@ -138,10 +138,6 @@ static int __init fscache_init(void)
unsigned int cpu;
int ret;

- ret = slow_work_register_user(THIS_MODULE);
- if (ret < 0)
- goto error_slow_work;
-
fscache_object_max_active =
clamp_val(nr_cpus, fscache_object_max_active, WQ_MAX_ACTIVE);

@@ -213,8 +209,6 @@ error_proc:
error_op_wq:
destroy_workqueue(fscache_object_wq);
error_object_wq:
- slow_work_unregister_user(THIS_MODULE);
-error_slow_work:
return ret;
}

@@ -233,7 +227,6 @@ static void __exit fscache_exit(void)
fscache_proc_cleanup();
destroy_workqueue(fscache_op_wq);
destroy_workqueue(fscache_object_wq);
- slow_work_unregister_user(THIS_MODULE);
printk(KERN_NOTICE "FS-Cache: Unloaded\n");
}

diff --git a/include/linux/fscache-cache.h b/include/linux/fscache-cache.h
index aed1cf5..5816e56 100644
--- a/include/linux/fscache-cache.h
+++ b/include/linux/fscache-cache.h
@@ -20,7 +20,6 @@

#include <linux/fscache.h>
#include <linux/sched.h>
-#include <linux/slow-work.h>
#include <linux/workqueue.h>

#define NR_MAXCACHES BITS_PER_LONG
--
1.6.4.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/