[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DFF82E2.1010409@redhat.com>
Date: Tue, 21 Jun 2011 01:26:58 +0800
From: Cong Wang <amwang@...hat.com>
To: Mel Gorman <mgorman@...e.de>
CC: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
Andrea Arcangeli <aarcange@...hat.com>,
Rik van Riel <riel@...hat.com>,
Johannes Weiner <jweiner@...hat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
linux-mm@...ck.org
Subject: Re: [PATCH 3/3] mm: print information when THP is disabled automatically
于 2011年06月21日 01:01, Mel Gorman 写道:
> On Tue, Jun 21, 2011 at 12:34:30AM +0800, Amerigo Wang wrote:
>> Print information when THP is disabled automatically so that
>> users can find this info in dmesg.
>>
>> Signed-off-by: WANG Cong<amwang@...hat.com>
>> ---
>> mm/huge_memory.c | 5 ++++-
>> 1 files changed, 4 insertions(+), 1 deletions(-)
>>
>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>> index 7fb44cc..07679da 100644
>> --- a/mm/huge_memory.c
>> +++ b/mm/huge_memory.c
>> @@ -544,8 +544,11 @@ static int __init hugepage_init(void)
>> * where the extra memory used could hurt more than TLB overhead
>> * is likely to save. The admin can still enable it through /sys.
>> */
>> - if (totalram_pages< (CONFIG_TRANSPARENT_HUGEPAGE_THRESHOLD<< (20 - PAGE_SHIFT)))
>> + if (totalram_pages< (CONFIG_TRANSPARENT_HUGEPAGE_THRESHOLD
>> + << (20 - PAGE_SHIFT))) {
>> + printk(KERN_INFO "hugepage: disabled auotmatically\n");
>> transparent_hugepage_flags = 0;
>> + }
>>
>> start_khugepaged();
>>
>
> Guess this doesn't hurt. You misspelled automatically though and
> mentioning "hugepage" could be confused with hugetlbfs.
>
Yeah, sorry for the typo.
But, there are many printk messages in the same file start with "hugepage:".
:-) I can send a patch to replace all of them with "THP" if you want...
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists