From: Mike Rapoport <rppt@linux.ibm.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: Matthew Wilcox <willy@infradead.org>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3 2/3] mm: Add PUD level pagetable account
Date: Sun, 3 Jul 2022 17:28:15 +0300 [thread overview]
Message-ID: <YsGnf33G/z1NOql1@linux.ibm.com> (raw)
In-Reply-To: <17df0d3c-caaf-ee34-f702-1d4e7674887f@linux.alibaba.com>
On Sun, Jul 03, 2022 at 10:06:32PM +0800, Baolin Wang wrote:
>
>
> On 7/3/2022 11:40 AM, Matthew Wilcox wrote:
> > On Fri, Jul 01, 2022 at 04:04:21PM +0800, Baolin Wang wrote:
> > > > Using pgtable_pud_page_ctor() and pgtable_pud_page_dtor() would be
> > > > consistent with what we currently have for PTEs and PMDs.
> > > >
> > > > This applies to all the additions of pgtable_page_dec() and
> > > > pgtable_page_inc().
> > >
> > > OK. I can add pgtable_pud_page_ctor() and pgtable_pud_page_dtor() helpers to
> > > keep consistent, which are just wrappers of pgtable_page_inc() and
> > > pgtable_page_dec().
> >
> > I think you misunderstand Mike.
> >
> > Don't add pgtable_page_inc() and pgtable_page_dec(). Just add
> > pgtable_pud_page_ctor() and pgtable_pud_page_dtor(). At least, that
> > was what I said last time you posted these patches.
>
> My concern is that I need another helpers for kernel page table allocation
> helpers, if only adding pgtable_pud_page_ctor() and pgtable_pud_page_dtor()
> like below:
>
> static inline void pgtable_pud_page_ctor(struct page *page)
> {
> __SetPageTable(page);
> inc_lruvec_page_state(page, NR_PAGETABLE);
> }
>
> static inline void pgtable_pud_page_dtor(struct page *page)
> {
> __ClearPageTable(page);
> dec_lruvec_page_state(page, NR_PAGETABLE);
> }
>
> So for kernel pte page table allocation, I need another similar helpers like
> below. However they do the samething with
> pgtable_pud_page_ctor/pgtable_pud_page_dtor, so I am not sure this is good
> for adding these duplicate code.
>
> static inline void pgtable_kernel_pte_page_ctor(struct page *page)
> {
> __SetPageTable(page);
> inc_lruvec_page_state(page, NR_PAGETABLE);
> }
>
> static inline void pgtable_kernel_pte_page_dtor(struct page *page)
> {
> __ClearPageTable(page);
> dec_lruvec_page_state(page, NR_PAGETABLE);
> }
>
> Instead adding a common helpers seems more readable to me, which can also
> simplify original pgtable_pmd_page_dtor()/pgtable_pmd_page_ctor(). Something
> like below.
>
> static inline void pgtable_page_inc(struct page *page)
> {
> __SetPageTable(page);
> inc_lruvec_page_state(page, NR_PAGETABLE);
> }
>
> static inline void pgtable_page_dec(struct page *page)
> {
> __ClearPageTable(page);
> dec_lruvec_page_state(page, NR_PAGETABLE);
> }
>
> static inline void pgtable_pud_page_ctor(struct page *page)
> {
> pgtable_page_inc(page);
> }
>
> static inline void pgtable_pud_page_dtor(struct page *page)
> {
> pgtable_page_dec(page);
> }
>
> For kernel pte page table, we can just use
> pgtable_page_inc/pgtable_page_dec(), or adding
> pgtable_kernel_pte_page_ctor/pgtable_kernel_pte_page_dtor, which just
> wrappers of pgtable_page_inc() and pgtable_page_dec().
>
> Matthew and Mike, how do you think? Thanks.
I actually meant to add pgtable_pud_page_ctor/dtor() as a wrapper for the
new helper to keep pud tables allocation consistent with pmd and pte and
as a provision for the time we'll have per-page pud locks.
For the accounting of the kernel page tables a new helper does make sense
because there are no locks to initialize for the kernel page tables.
I can't say that I'm happy with the pgtable_page_inc/dec names, though.
Maybe page_{set,clear}_pgtable()?
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2022-07-03 14:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:11 [RFC PATCH v3 0/3] Add PUD and kernel PTE " Baolin Wang
2022-06-30 11:11 ` [RFC PATCH v3 1/3] mm: Factor out the pagetable pages account into new helper function Baolin Wang
2022-06-30 14:11 ` Mike Rapoport
2022-07-01 8:00 ` Baolin Wang
2022-07-02 10:15 ` Mike Rapoport
2022-07-03 13:48 ` Baolin Wang
2022-06-30 11:11 ` [RFC PATCH v3 2/3] mm: Add PUD level pagetable account Baolin Wang
2022-06-30 14:17 ` Mike Rapoport
2022-07-01 8:04 ` Baolin Wang
2022-07-03 3:40 ` Matthew Wilcox
2022-07-03 14:06 ` Baolin Wang
2022-07-03 14:28 ` Mike Rapoport [this message]
2022-07-03 14:49 ` Baolin Wang
2022-07-03 14:52 ` Matthew Wilcox
2022-07-03 15:07 ` Baolin Wang
2022-07-03 3:47 ` Matthew Wilcox
2022-07-03 14:18 ` Mike Rapoport
2022-06-30 11:11 ` [RFC PATCH v3 3/3] mm: Add kernel PTE level pagetable pages account Baolin Wang
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=YsGnf33G/z1NOql1@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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