From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: n-horiguchi@ah.jp.nec.com
Cc: kosaki.motohiro@gmail.com, linux-mm@kvack.org,
akpm@linux-foundation.org, rientjes@google.com,
andi@firstfloor.org, fengguang.wu@intel.com, aarcange@redhat.com,
kamezawa.hiroyu@jp.fujitsu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] pagemap: avoid splitting thp when reading /proc/pid/pagemap
Date: Tue, 03 Jan 2012 16:06:28 -0500 [thread overview]
Message-ID: <4F036DD4.2060709@jp.fujitsu.com> (raw)
In-Reply-To: <4F035FF6.7020206@ah.jp.nec.com>
On 1/3/2012 3:07 PM, Naoya Horiguchi wrote:
> Hi,
>
> Thank you for your reviewing.
>
> On Thu, Dec 29, 2011 at 10:39:18PM -0500, KOSAKI Motohiro wrote:
> ...
>>> --- 3.2-rc5.orig/fs/proc/task_mmu.c
>>> +++ 3.2-rc5/fs/proc/task_mmu.c
>>> @@ -600,6 +600,9 @@ struct pagemapread {
>>> u64 *buffer;
>>> };
>>>
>>> +#define PAGEMAP_WALK_SIZE (PMD_SIZE)
>>> +#define PAGEMAP_WALK_MASK (PMD_MASK)
>>> +
>>> #define PM_ENTRY_BYTES sizeof(u64)
>>> #define PM_STATUS_BITS 3
>>> #define PM_STATUS_OFFSET (64 - PM_STATUS_BITS)
>>> @@ -658,6 +661,22 @@ static u64 pte_to_pagemap_entry(pte_t pte)
>>> return pme;
>>> }
>>>
>>> +#ifdef CONFIG_TRANSPARENT_HUGEPAGE
>>> +static u64 thp_pte_to_pagemap_entry(pte_t pte, int offset)
>>> +{
>>> + u64 pme = 0;
>>> + if (pte_present(pte))
>>
>> When does pte_present() return 0?
>
> It does when the page pointed to by pte is swapped-out, under page migration,
> or HWPOISONed. But currenly it can't happen on thp because thp will be
> splitted before these operations are processed.
> So this if-sentense is not necessary for now, but I think it's not a bad idea
> to put it now to prepare for future implementation.
You certainly need to add a comment. otherwise you add *unnecessary* complexity
and people is going to be puzzled.
>>> + pfn = thp_pte_to_pagemap_entry(*(pte_t *)pmd,
>>> + offset);
>>
>> This (pte_t*) cast looks introduce new implicit assumption. Please don't
>> put x86 assumption here directly.
>
> OK, I think it's better to write a separate patch for this job because
> similar assumption is used in smaps_pte_range() and gather_pte_stats().
Sound sane.
>>> + } else {
>>> + spin_unlock(&walk->mm->page_table_lock);
>>> + }
>>
>> coding standard violation. plz run check_patch.pl.
>
> checkpatch.pl says nothing for here. According to Documentation/CodingStyle,
> "no braces for single statement" rule is not applicable for else-blocks with
> one statement if corresponding if-blocks have multiple statements.
ok
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-01-03 21:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 22:23 [PATCH 0/4 v2] pagemap handles transparent hugepage Naoya Horiguchi
2011-12-21 22:23 ` [PATCH 1/4] pagemap: avoid splitting thp when reading /proc/pid/pagemap Naoya Horiguchi
2011-12-26 8:26 ` KAMEZAWA Hiroyuki
2011-12-30 3:39 ` KOSAKI Motohiro
2012-01-03 20:07 ` Naoya Horiguchi
2012-01-03 21:06 ` KOSAKI Motohiro [this message]
2012-01-03 21:31 ` Naoya Horiguchi
2012-01-04 23:50 ` Andrew Morton
2012-01-05 16:28 ` Naoya Horiguchi
2011-12-21 22:23 ` [PATCH 2/4] thp: optimize away unnecessary page table locking Naoya Horiguchi
2011-12-22 13:04 ` Hillf Danton
2011-12-22 16:01 ` Naoya Horiguchi
2011-12-30 3:59 ` KOSAKI Motohiro
2012-01-03 20:08 ` Naoya Horiguchi
2011-12-21 22:23 ` [PATCH 3/4] pagemap: export KPF_THP Naoya Horiguchi
2011-12-26 8:40 ` KAMEZAWA Hiroyuki
2011-12-30 4:01 ` KOSAKI Motohiro
2012-01-04 23:55 ` Andrew Morton
2011-12-21 22:23 ` [PATCH 4/4] pagemap: document KPF_THP and make page-types aware of it Naoya Horiguchi
2011-12-26 8:42 ` KAMEZAWA Hiroyuki
2011-12-30 4:02 ` KOSAKI Motohiro
2012-01-04 23:57 ` Andrew Morton
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=4F036DD4.2060709@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).