From: Guozhonghua <guozhonghua@h3c.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [Ocfs2-users] o2locktop introduction
Date: Wed, 20 Mar 2019 10:44:01 +0000 [thread overview]
Message-ID: <71604351584F6A4EBAE558C676F37CA4013BFE7DA0@H3CMLB12-EX.srv.huawei-3com.com> (raw)
Good News.
Thanks.
> -----????-----
> ???: ocfs2-users-bounces at oss.oracle.com
> [mailto:ocfs2-users-bounces at oss.oracle.com] ?? Gang He
> ????: 2019?3?20? 18:07
> ???: ocfs2-devel at oss.oracle.com; ocfs2-tools-devel at oss.oracle.com;
> ocfs2-users at oss.oracle.com
> ??: [Ocfs2-users] o2locktop introduction
>
> Hello Guys,
>
> We wrote a tool with Python, which is used to display DLM lock usages in a OCFS2
> cluster.
> o2locktop is a top-like OCFS2 DLM lock monitor, it displays DLM lock usages via
> querying OCFS2 file system statistics from the specified nodes.
> Therefore, OCFS2 kernel modules must enable OCFS2_FS_STATS configuration
> option when compiling.
> If you want to know if the current OCFS2 kernel modules enable OCFS2_FS_STATS
> setting, you can refer to /boot/config-`uname -r` file.
> You can utilize o2locktop to detect the hot files/directories, whose DLM locks are
> frequently referenced among the cluster.
> You can get the maximal wait time per DLM lock, this helps you identify which hot
> files/directories should be decoupled for improving file access performance.
> For more details, please visit the link
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ganghe_o2lockt
> op&d=DwIFAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=wXmkJN
> AUtutY0U9inuQWCbzSSRji5zLpyR0a_Mek4jM&m=93wGE0zLoHuCKph4-kgDwzuZm9
> oc1J4Mhz9PxVbVxZc&s=lVluTYcXetvTd2GFdOJLcqDtQcWFhVrDY5I6MI1r_Ow&e=
> This tool is expected to be used for SUSE customer, if you are interested, welcome
> to use, to contribute, suggestions, etc.
>
> Thanks a lot.
> Gang
>
>
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-users
reply other threads:[~2019-03-20 10:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=71604351584F6A4EBAE558C676F37CA4013BFE7DA0@H3CMLB12-EX.srv.huawei-3com.com \
--to=guozhonghua@h3c.com \
--cc=ocfs2-devel@oss.oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.