From: Xishi Qiu <qiuxishi@huawei.com>
To: Linux MM <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [question] hugetlb: how to find who use hugetlb?
Date: Tue, 20 Sep 2016 10:46:04 +0800 [thread overview]
Message-ID: <57E0A2EC.7050809@huawei.com> (raw)
In-Reply-To: <57DF4FEA.9080509@huawei.com>
On 2016/9/19 10:39, Xishi Qiu wrote:
> On my system, I set HugePages_Total to 2G(1024 x 2M), and I use 1G hugetlb,
> but the HugePages_Free is not 1G(512 x 2M), it is 280(280 x 2M) left,
> HugePages_Rsvd is 0, it seems someone use 232(232 x 2M) hugetlb additionally.
>
> So how to find who use the additional hugetlb?
>
> I search every process and find the total hugetlb size is only 1G,
> cat /proc/xx/smaps | grep KernelPageSize, then account the vma size
> which KernelPageSize is 2048 kB.
>
> Thanks,
> Xishi Qiu
>
I kill the processes which use hugetlb, and set 0 to nr_hugepages.
My kernel version is v3.10
meminfo:
HugePages_Total: 232
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 232
Hugepagesize: 2048 kB
"cat /proc/*/smaps | grep KernelPageSize| grep 2048" shows nothing.
linux-ZSfbIr:/home # mount | grep hugetlb
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
nodev on /dev/hugepages type hugetlbfs (rw,relatime)
linux-ZSfbIr:/home # ll /dev/hugepages/
total 0
linux-ZSfbIr:/home # ll /sys/fs/cgroup/hugetlb/
total 0
-rw-r--r-- 1 root root 0 Sep 13 08:10 cgroup.clone_children
--w--w--w- 1 root root 0 Sep 13 08:10 cgroup.event_control
-rw-r--r-- 1 root root 0 Sep 13 08:10 cgroup.procs
-r--r--r-- 1 root root 0 Sep 13 08:10 cgroup.sane_behavior
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.1GB.failcnt
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.1GB.limit_in_bytes
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.1GB.max_usage_in_bytes
-r--r--r-- 1 root root 0 Sep 13 08:10 hugetlb.1GB.usage_in_bytes
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.2MB.failcnt
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.2MB.limit_in_bytes
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.2MB.max_usage_in_bytes
-r--r--r-- 1 root root 0 Sep 13 08:10 hugetlb.2MB.usage_in_bytes
-rw-r--r-- 1 root root 0 Sep 13 08:10 notify_on_release
-rw-r--r-- 1 root root 0 Sep 13 08:10 release_agent
-rw-r--r-- 1 root root 0 Sep 13 08:10 tasks
linux-ZSfbIr:/home #
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Xishi Qiu <qiuxishi@huawei.com>
To: Linux MM <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [question] hugetlb: how to find who use hugetlb?
Date: Tue, 20 Sep 2016 10:46:04 +0800 [thread overview]
Message-ID: <57E0A2EC.7050809@huawei.com> (raw)
In-Reply-To: <57DF4FEA.9080509@huawei.com>
On 2016/9/19 10:39, Xishi Qiu wrote:
> On my system, I set HugePages_Total to 2G(1024 x 2M), and I use 1G hugetlb,
> but the HugePages_Free is not 1G(512 x 2M), it is 280(280 x 2M) left,
> HugePages_Rsvd is 0, it seems someone use 232(232 x 2M) hugetlb additionally.
>
> So how to find who use the additional hugetlb?
>
> I search every process and find the total hugetlb size is only 1G,
> cat /proc/xx/smaps | grep KernelPageSize, then account the vma size
> which KernelPageSize is 2048 kB.
>
> Thanks,
> Xishi Qiu
>
I kill the processes which use hugetlb, and set 0 to nr_hugepages.
My kernel version is v3.10
meminfo:
HugePages_Total: 232
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 232
Hugepagesize: 2048 kB
"cat /proc/*/smaps | grep KernelPageSize| grep 2048" shows nothing.
linux-ZSfbIr:/home # mount | grep hugetlb
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
nodev on /dev/hugepages type hugetlbfs (rw,relatime)
linux-ZSfbIr:/home # ll /dev/hugepages/
total 0
linux-ZSfbIr:/home # ll /sys/fs/cgroup/hugetlb/
total 0
-rw-r--r-- 1 root root 0 Sep 13 08:10 cgroup.clone_children
--w--w--w- 1 root root 0 Sep 13 08:10 cgroup.event_control
-rw-r--r-- 1 root root 0 Sep 13 08:10 cgroup.procs
-r--r--r-- 1 root root 0 Sep 13 08:10 cgroup.sane_behavior
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.1GB.failcnt
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.1GB.limit_in_bytes
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.1GB.max_usage_in_bytes
-r--r--r-- 1 root root 0 Sep 13 08:10 hugetlb.1GB.usage_in_bytes
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.2MB.failcnt
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.2MB.limit_in_bytes
-rw-r--r-- 1 root root 0 Sep 13 08:10 hugetlb.2MB.max_usage_in_bytes
-r--r--r-- 1 root root 0 Sep 13 08:10 hugetlb.2MB.usage_in_bytes
-rw-r--r-- 1 root root 0 Sep 13 08:10 notify_on_release
-rw-r--r-- 1 root root 0 Sep 13 08:10 release_agent
-rw-r--r-- 1 root root 0 Sep 13 08:10 tasks
linux-ZSfbIr:/home #
>
>
next prev parent reply other threads:[~2016-09-20 2:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 2:39 [question] hugetlb: how to find who use hugetlb? Xishi Qiu
2016-09-19 2:39 ` Xishi Qiu
2016-09-20 2:46 ` Xishi Qiu [this message]
2016-09-20 2:46 ` Xishi Qiu
2016-09-20 4:05 ` Hillf Danton
2016-09-20 4:29 ` Xishi Qiu
2016-09-20 6:47 ` Hillf Danton
2016-09-20 7:09 ` Xishi Qiu
2016-09-20 7:15 ` Hillf Danton
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=57E0A2EC.7050809@huawei.com \
--to=qiuxishi@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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.