From: "Zi Yan" <ziy@nvidia.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Shuah Khan" <shuah@kernel.org>,
"John Hubbard" <jhubbard@nvidia.com>,
"Sandipan Das" <sandipan@linux.ibm.com>,
"David Hildenbrand" <david@redhat.com>,
"Yang Shi" <shy828301@gmail.com>,
"Mika Penttila" <mika.penttila@nextfour.com>
Subject: Re: [PATCH v3] mm: huge_memory: a new debugfs interface for splitting THP tests.
Date: Mon, 15 Mar 2021 14:37:39 -0400 [thread overview]
Message-ID: <D3A202E7-6F74-4937-A160-199032E15AC4@nvidia.com> (raw)
In-Reply-To: <20210315120748.nuw5vk6grmfacact@box>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
On 15 Mar 2021, at 8:07, Kirill A. Shutemov wrote:
> On Thu, Mar 11, 2021 at 07:57:12PM -0500, Zi Yan wrote:
>> From: Zi Yan <ziy@nvidia.com>
>>
>> We do not have a direct user interface of splitting the compound page
>> backing a THP
>
> But we do. You expand it.
>
>> and there is no need unless we want to expose the THP
>> implementation details to users. Make <debugfs>/split_huge_pages accept
>> a new command to do that.
>>
>> By writing "<pid>,<vaddr_start>,<vaddr_end>" to
>> <debugfs>/split_huge_pages, THPs within the given virtual address range
>> from the process with the given pid are split. It is used to test
>> split_huge_page function. In addition, a selftest program is added to
>> tools/testing/selftests/vm to utilize the interface by splitting
>> PMD THPs and PTE-mapped THPs.
>>
>
> Okay, makes sense.
>
> But it doesn't cover non-mapped THPs. tmpfs may have file backed by THP
> that mapped nowhere. Do we want to cover this case too?
Sure. It would be useful when large page in page cache too. I will send
v4 with tmpfs THP split. I will definitely need a review for it, since
I am not familiar with getting a page from a file path.
> Maybe have PID:<pid>,<vaddr_start>,<vaddr_end> and
> FILE:<path>,<off_start>,<off_end> ?
Or just check input[0] == ‘/‘ for file path input.
—
Best Regards,
Yan Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2021-03-15 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 0:57 Zi Yan
[not found] ` <20210315120748.nuw5vk6grmfacact@box>
2021-03-15 18:37 ` Zi Yan [this message]
2021-03-15 19:13 ` Yang Shi
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=D3A202E7-6F74-4937-A160-199032E15AC4@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mika.penttila@nextfour.com \
--cc=sandipan@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=shy828301@gmail.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