ocfs2/dlm: Track number of mles

The lifetime of a mle is limited to the duration of the lockres mastery
process. While typically this lifetime is fairly short, we have noticed
the number of mles explode under certain circumstances. This patch tracks
the number of each different types of mles and should help us determine
how best to speed up the mastery process.

Signed-off-by: Sunil Mushran <sunil.mushran@oracle.com>
Signed-off-by: Mark Fasheh <mfasheh@suse.com>

1 files changed, 4 insertions, 1 deletions

diff --git a/fs/ocfs2/dlm/dlmcommon.h b/fs/ocfs2/dlm/dlmcommon.h
index aa55271a7aca..67b3447a292e 100644
--- a/fs/ocfs2/dlm/dlmcommon.h
+++ b/fs/ocfs2/dlm/dlmcommon.h
@@ -52,7 +52,8 @@
 enum dlm_mle_type {
         DLM_MLE_BLOCK,
         DLM_MLE_MASTER,
-        DLM_MLE_MIGRATION
+        DLM_MLE_MIGRATION,
+        DLM_MLE_NUM_TYPES
 };
 
 struct dlm_lock_name {
@@ -156,6 +157,8 @@ struct dlm_ctxt
         struct list_head mle_hb_events;
 
         /* these give a really vague idea of the system load */
+        atomic_t mle_tot_count[DLM_MLE_NUM_TYPES];
+        atomic_t mle_cur_count[DLM_MLE_NUM_TYPES];
         atomic_t local_resources;
         atomic_t remote_resources;
         atomic_t unknown_resources;