From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: aarcange@redhat.com, akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/THP: Don't use HPAGE_SHIFT in transparent hugepage code
Date: Tue, 07 May 2013 08:58:13 +0530 [thread overview]
Message-ID: <87wqrbzcxe.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130506222719.GA23653@shutemov.name>
"Kirill A. Shutemov" <kirill@shutemov.name> writes:
> On Tue, May 07, 2013 at 02:22:32AM +0530, Aneesh Kumar K.V wrote:
>> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
>>
>> For architectures like powerpc that support multiple explicit hugepage
>> sizes, HPAGE_SHIFT indicate the default explicit hugepage shift. For
>> THP to work the hugepage size should be same as PMD_SIZE. So use
>> PMD_SHIFT directly. So move the define outside CONFIG_TRANSPARENT_HUGEPAGE
>> #ifdef because we want to use these defines in generic code with
>> if (pmd_trans_huge()) conditional.
>>
>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>> ---
>> include/linux/huge_mm.h | 10 +++-------
>> 1 file changed, 3 insertions(+), 7 deletions(-)
>>
>> diff --git a/include/linux/huge_mm.h b/include/linux/huge_mm.h
>> index 528454c..cc276d2 100644
>> --- a/include/linux/huge_mm.h
>> +++ b/include/linux/huge_mm.h
>> @@ -58,12 +58,11 @@ extern pmd_t *page_check_address_pmd(struct page *page,
>>
>> #define HPAGE_PMD_ORDER (HPAGE_PMD_SHIFT-PAGE_SHIFT)
>> #define HPAGE_PMD_NR (1<<HPAGE_PMD_ORDER)
>> +#define HPAGE_PMD_SHIFT PMD_SHIFT
>
> What about:
>
> #ifndef HPAGE_PMD_SHIFT
> #define HPAGE_PMD_SHIFT HPAGE_SHIFT
> #endif
>
> And define HPAGE_PMD_SHIFT in arch code if HPAGE_SHIFT is not
> suitable?
That would work for me provided the BUILD_BUG_ON is also taken care.
But is there a reason why we want to do that ? Will any value other
than PMD_SHIFT work ?
The below patch shows how we want to use these. To avoid those
BUILD_BUG_ON I ended up doing HUGE_PAGE_SIZE and HUGE_PAGE_MASK
https://lists.ozlabs.org/pipermail/linuxppc-dev/2013-April/105631.html
-aneesh
--
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>
prev parent reply other threads:[~2013-05-07 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 20:52 Aneesh Kumar K.V
2013-05-06 22:07 ` Kirill A. Shutemov
2013-05-06 22:27 ` Kirill A. Shutemov
2013-05-07 3:28 ` Aneesh Kumar K.V [this message]
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=87wqrbzcxe.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kirill@shutemov.name \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox