From: "Huang, Ying" <ying.huang@intel.com>
To: Peter Xu <peterx@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Nadav Amit <nadav.amit@gmail.com>,
Hugh Dickins <hughd@google.com>,
David Hildenbrand <david@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH RFC 1/4] mm/swap: Add swp_offset_pfn() to fetch PFN from swap entry
Date: Tue, 02 Aug 2022 09:22:52 +0800 [thread overview]
Message-ID: <87czdjjv6b.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <YuhTvDIC26trwr18@xz-m1.local> (Peter Xu's message of "Mon, 1 Aug 2022 18:29:16 -0400")
Peter Xu <peterx@redhat.com> writes:
> On Mon, Aug 01, 2022 at 11:13:58AM +0800, Huang, Ying wrote:
>> > +/*
>> > + * This should only be called upon a pfn swap entry to get the PFN stored
>> > + * in the swap entry. Please refers to is_pfn_swap_entry() for definition
>> > + * of pfn swap entry.
>> > + */
>> > +static inline unsigned long swp_offset_pfn(swp_entry_t entry)
>> > +{
>>
>> Is it good to call is_pfn_swap_entry() here for debug that can be
>> eliminated in the production kernel?
>
> Sure, I'll add a VM_BUG_ON() there in the next spin.
>
>>
>> > + return swp_offset(entry) & SWP_PFN_MASK;
>> > +}
>> > +
>> > /* check whether a pte points to a swap entry */
>> > static inline int is_swap_pte(pte_t pte)
>> > {
>> > @@ -369,7 +387,7 @@ static inline int pte_none_mostly(pte_t pte)
>> >
>> > static inline struct page *pfn_swap_entry_to_page(swp_entry_t entry)
>> > {
>> > - struct page *p = pfn_to_page(swp_offset(entry));
>> > + struct page *p = pfn_to_page(swp_offset_pfn(entry));
>> >
>> > /*
>> > * Any use of migration entries may only occur while the
>> > @@ -387,6 +405,9 @@ static inline struct page *pfn_swap_entry_to_page(swp_entry_t entry)
>> > */
>> > static inline bool is_pfn_swap_entry(swp_entry_t entry)
>> > {
>> > + /* Make sure the swp offset can always store the needed fields */
>> > + BUILD_BUG_ON(SWP_TYPE_SHIFT < SWP_PFN_BITS);
>>
>> BUILD_BUG_ON(SWP_TYPE_SHIFT <= SWP_PFN_BITS);
>
> Logiclaly it's okay to have SWP_TYPE_SHIFT==SWP_PFN_BITS?
Sorry, I misunderstood the original code. Please ignore this comment.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2022-08-02 1:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 1:40 [PATCH RFC 0/4] mm: Remember young bit for migration entries Peter Xu
2022-07-29 1:40 ` [PATCH RFC 1/4] mm/swap: Add swp_offset_pfn() to fetch PFN from swap entry Peter Xu
2022-08-01 3:13 ` Huang, Ying
2022-08-01 22:29 ` Peter Xu
2022-08-02 1:22 ` Huang, Ying [this message]
2022-07-29 1:40 ` [PATCH RFC 2/4] mm: Remember young bit for page migrations Peter Xu
2022-07-29 1:40 ` [PATCH RFC 3/4] mm/x86: Use SWP_TYPE_BITS in 3-level swap macros Peter Xu
2022-07-29 1:40 ` [PATCH RFC 4/4] mm/x86: Define __ARCH_SWP_OFFSET_BITS Peter Xu
2022-07-29 17:07 ` [PATCH RFC 0/4] mm: Remember young bit for migration entries Nadav Amit
2022-07-29 22:43 ` Peter Xu
2022-08-01 3:20 ` Huang, Ying
2022-08-01 5:33 ` Huang, Ying
2022-08-01 22:25 ` Peter Xu
2022-08-01 8:21 ` David Hildenbrand
2022-08-01 22:35 ` Peter Xu
2022-08-02 12:06 ` David Hildenbrand
2022-08-02 20:14 ` Peter Xu
2022-08-02 20:23 ` David Hildenbrand
2022-08-02 20:35 ` Peter Xu
2022-08-02 20:59 ` David Hildenbrand
2022-08-02 22:15 ` Peter Xu
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=87czdjjv6b.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.com \
--cc=peterx@redhat.com \
--cc=vbabka@suse.cz \
/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