From: Mike Rapoport <rppt@kernel.org>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: akpm@linux-foundation.org, pasha.tatashin@soleen.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] add page_ext_data to get client data in page_ext
Date: Wed, 19 Jul 2023 12:44:21 +0300 [thread overview]
Message-ID: <20230719094421.GI1901145@kernel.org> (raw)
In-Reply-To: <20230718145812.1991717-1-shikemeng@huaweicloud.com>
On Tue, Jul 18, 2023 at 10:58:09PM +0800, Kemeng Shi wrote:
> Current client get data from page_ext by adding offset which is auto
> generated in page_ext core and expose the data layout design insdie
> page_ext core. This series adds a page_ext_data to hide offset from
> client. Thanks!
Implementers of page_ext_operations are anyway intimately related to
page_ext, so I'm not convinced this has any value.
> Kemeng Shi (3):
> mm/page_ext: add common function to get client data from page_ext
> mm/page_ext: use page_ext_data helper in page_table_check
> mm/page_ext: use page_ext_data helper in page_owner
>
> include/linux/page_ext.h | 6 ++++++
> mm/page_owner.c | 2 +-
> mm/page_table_check.c | 2 +-
> 3 files changed, 8 insertions(+), 2 deletions(-)
>
> --
> 2.30.0
>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-07-19 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 14:58 Kemeng Shi
2023-07-18 14:58 ` [PATCH 1/3] mm/page_ext: add common function to get client data from page_ext Kemeng Shi
2023-07-18 14:58 ` [PATCH 2/3] mm/page_ext: use page_ext_data helper in page_table_check Kemeng Shi
2023-07-19 9:44 ` Mike Rapoport [this message]
2023-07-20 2:38 ` [PATCH 0/3] add page_ext_data to get client data in page_ext Kemeng Shi
2023-07-20 5:37 ` Mike Rapoport
2023-07-20 8:37 ` Kemeng Shi
2023-08-11 21:39 ` Andrew Morton
2023-08-15 6:43 ` Mike Rapoport
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=20230719094421.GI1901145@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=shikemeng@huaweicloud.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