linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Barry Song <21cnbao@gmail.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Zenghui Yu <yuzenghui@huawei.com>,
	"Matthew Wilcox" <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>,
	"Kefeng Wang" <wangkefeng.wang@huawei.com>,
	Zi Yan <ziy@nvidia.com>, Alistair Popple <apopple@nvidia.com>,
	<linux-mm@kvack.org>
Subject: Re: [RFC PATCH v1] tools/mm: Add thpmaps script to dump THP usage info
Date: Tue, 9 Jan 2024 20:15:54 -0800	[thread overview]
Message-ID: <a0c227f4-4f2c-4025-a508-c60fe05735c2@nvidia.com> (raw)
In-Reply-To: <CAGsJ_4zFR2u9+q6ZGV6nj+hYsDAp0z5P447vndUhc=_A1Bc6uQ@mail.gmail.com>

On 1/9/24 19:51, Barry Song wrote:
> On Wed, Jan 10, 2024 at 11:35 AM John Hubbard <jhubbard@nvidia.com> wrote:
...
>> Hi Ryan,
>>
>> One thing that immediately came up during some recent testing of mTHP
>> on arm64: the pid requirement is sometimes a little awkward. I'm running
>> tests on a machine at a time for now, inside various containers and
>> such, and it would be nice if there were an easy way to get some numbers
>> for the mTHPs across the whole machine.
>>
>> I'm not sure if that changes anything about thpmaps here. Probably
>> this is fine as-is. But I wanted to give some initial reactions from
>> just some quick runs: the global state would be convenient.
> 
> +1. but this seems to be impossible by scanning pagemap?
> so may we add this statistics information in kernel just like
> /proc/meminfo or a separate /proc/mthp_info?
> 

Yes. From my perspective, it looks like the global stats are more useful
initially, and the more detailed per-pid or per-cgroup stats are the
next level of investigation. So feels odd to start with the more
detailed stats.

However, Ryan did clearly say, above, "In future we may wish to
introduce stats directly into the kernel (e.g. smaps or similar)". And
earlier he ran into some pushback on trying to set up /proc or /sys
values because this is still such an early feature.

I wonder if we could put the global stats in debugfs for now? That's
specifically supposed to be a "we promise *not* to keep this ABI stable"
location.


thanks,
-- 
John Hubbard
NVIDIA



  reply	other threads:[~2024-01-10  4:16 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 15:38 Ryan Roberts
2024-01-03  6:44 ` Barry Song
2024-01-03  8:07   ` William Kucharski
2024-01-03  8:24     ` Ryan Roberts
2024-01-03  9:16       ` Barry Song
2024-01-03  9:35         ` Ryan Roberts
2024-01-03 10:09           ` William Kucharski
2024-01-03 10:20             ` Ryan Roberts
2024-01-04 22:48               ` John Hubbard
2024-01-05  8:35                 ` Ryan Roberts
2024-01-05 11:30                   ` William Kucharski
2024-01-05 23:07                     ` John Hubbard
2024-01-05 23:18                   ` John Hubbard
2024-01-10  8:43                     ` Ryan Roberts
2024-01-05  8:40 ` Ryan Roberts
2024-01-10  3:34 ` John Hubbard
2024-01-10  3:51   ` Barry Song
2024-01-10  4:15     ` John Hubbard [this message]
2024-01-10  8:02       ` Barry Song
2024-01-10  8:58         ` Ryan Roberts
2024-01-10  9:09           ` Barry Song
2024-01-10  9:20             ` Ryan Roberts
2024-01-10 10:23             ` Ryan Roberts
2024-01-10 10:30               ` Barry Song
2024-01-10 10:38                 ` Ryan Roberts
2024-01-10 10:42                   ` David Hildenbrand
2024-01-10 10:55                     ` Ryan Roberts
2024-01-10 11:00                       ` David Hildenbrand
2024-01-10 11:20                         ` Ryan Roberts
2024-01-10 11:24                           ` David Hildenbrand
2024-01-10 11:38                           ` Barry Song
2024-01-10 11:59                             ` Ryan Roberts
2024-01-10 12:05                               ` Barry Song
2024-01-10 12:12                                 ` David Hildenbrand
2024-01-10 15:19                                   ` Zi Yan
2024-01-10 15:27                                     ` David Hildenbrand
2024-01-10 22:14                               ` Barry Song
2024-01-11 12:25                                 ` Ryan Roberts
2024-01-11 13:18                                   ` David Hildenbrand
2024-01-11 20:21                                     ` Barry Song
2024-01-11 20:28                                       ` David Hildenbrand
2024-01-12  6:03                                         ` Barry Song
2024-01-12 10:44                                           ` Ryan Roberts
2024-01-12 10:18                                     ` Ryan Roberts
2024-01-17 15:49                                       ` David Hildenbrand
2024-01-11 20:45                                   ` Barry Song
2024-01-12 10:25                                     ` Ryan Roberts
2024-01-10 23:34                           ` Barry Song
2024-01-10 10:48                   ` Barry Song
2024-01-10 10:54                     ` David Hildenbrand
2024-01-10 10:58                       ` Ryan Roberts
2024-01-10 11:02                         ` David Hildenbrand
2024-01-10 11:07                         ` Barry Song

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=a0c227f4-4f2c-4025-a508-c60fe05735c2@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --cc=yuzenghui@huawei.com \
    --cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox