From: zhong jiang <zhongjiang@huawei.com>
To: mel@csn.ul.ie
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Have some confusion about the pfn_valid() ?
Date: Sat, 6 Feb 2016 16:14:07 +0800 [thread overview]
Message-ID: <56B5AB4F.3030809@huawei.com> (raw)
Hi
In my opinion, pfn_valid() is meant to be able to tell if a given PFN has valid
section, and That section can contain corresponding mem_map. but, the section can
be has holes, the corresponding mem_map also be allcoated, resulting in treating
the PFN as valid incorrect.
what's problem for the interpretation of the above?
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: zhong jiang <zhongjiang@huawei.com>
To: <mel@csn.ul.ie>
Cc: <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Have some confusion about the pfn_valid() ?
Date: Sat, 6 Feb 2016 16:14:07 +0800 [thread overview]
Message-ID: <56B5AB4F.3030809@huawei.com> (raw)
Hi
In my opinion, pfn_valid() is meant to be able to tell if a given PFN has valid
section, and That section can contain corresponding mem_map. but, the section can
be has holes, the corresponding mem_map also be allcoated, resulting in treating
the PFN as valid incorrect.
what's problem for the interpretation of the above?
next reply other threads:[~2016-02-06 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 8:14 zhong jiang [this message]
2016-02-06 8:14 ` Have some confusion about the pfn_valid() ? zhong jiang
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=56B5AB4F.3030809@huawei.com \
--to=zhongjiang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.