From f03352540563670e92e7d06780b7fb0d1f97b302 Mon Sep 17 00:00:00 2001 From: glebius Date: Tue, 26 Nov 2013 10:34:34 +0000 Subject: [PATCH] Fix build. --- sys/fs/nfsclient/nfs_clkdtrace.c | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/sys/fs/nfsclient/nfs_clkdtrace.c b/sys/fs/nfsclient/nfs_clkdtrace.c index cf3d8b09f10f..5e6e58cff490 100644 --- a/sys/fs/nfsclient/nfs_clkdtrace.c +++ b/sys/fs/nfsclient/nfs_clkdtrace.c @@ -176,21 +176,6 @@ static dtrace_pops_t dtnfsclient_pops = { static dtrace_provider_id_t dtnfsclient_id; -/* - * Most probes are generated from the above RPC table, but for access and - * attribute caches, we have specific IDs we recognize and handle specially - * in various spots. - */ -extern uint32_t nfscl_accesscache_flush_done_id; -extern uint32_t nfscl_accesscache_get_hit_id; -extern uint32_t nfscl_accesscache_get_miss_id; -extern uint32_t nfscl_accesscache_load_done_id; - -extern uint32_t nfscl_attrcache_flush_done_id; -extern uint32_t nfscl_attrcache_get_hit_id; -extern uint32_t nfscl_attrcache_get_miss_id; -extern uint32_t nfscl_attrcache_load_done_id; - /* * When tracing on a procedure is enabled, the DTrace ID for an RPC event is * stored in one of these two NFS client-allocated arrays; 0 indicates that