From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: "Barry Song" <21cnbao@gmail.com>,
"Huang, Ying" <ying.huang@intel.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
LAK <linux-arm-kernel@lists.infradead.org>,
Linux-MM <linux-mm@kvack.org>,
"Steven Price" <steven.price@arm.com>,
"Andrea Arcangeli" <aarcange@redhat.com>, 郭健 <guojian@oppo.com>,
hanchuanhua <hanchuanhua@oppo.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Hugh Dickins" <hughd@google.com>,
LKML <linux-kernel@vger.kernel.org>,
"Minchan Kim" <minchan@kernel.org>,
"Yang Shi" <shy828301@gmail.com>,
"Barry Song" <v-songbaohua@oppo.com>,
"张诗明(Simon Zhang)" <zhangshiming@oppo.com>
Subject: Re: [RESEND PATCH v3] arm64: enable THP_SWAP for arm64
Date: Wed, 20 Jul 2022 10:17:16 +0100 [thread overview]
Message-ID: <20220720091716.GA15752@willie-the-truck> (raw)
In-Reply-To: <cc22ee37-2134-0b51-5f4d-8b2cc4688f8c@arm.com>
On Wed, Jul 20, 2022 at 08:06:42AM +0530, Anshuman Khandual wrote:
> On 7/20/22 07:16, Barry Song wrote:
> > On Tue, Jul 19, 2022 at 4:04 PM Anshuman Khandual
> > <anshuman.khandual@arm.com> wrote:
> >> On 7/19/22 09:29, Barry Song wrote:
> >>> On Tue, Jul 19, 2022 at 3:35 PM Anshuman Khandual
> >>> <anshuman.khandual@arm.com> wrote:
> >>>> On 7/19/22 08:58, Huang, Ying wrote:
> >>>>> Anshuman Khandual <anshuman.khandual@arm.com> writes:
> >>>>>>>> How about the following?
> >>>>>>>>
> >>>>>>>> static inline bool arch_wants_thp_swap(void)
> >>>>>>>> {
> >>>>>>>> return IS_ENABLED(ARCH_WANTS_THP_SWAP);
> >>>>>>>> }
> >>>>>>>
> >>>>>>> This looks good. then i'll need to change arm64 to
> >>>>>>>
> >>>>>>> +static inline bool arch_thp_swp_supported(void)
> >>>>>>> +{
> >>>>>>> + return IS_ENABLED(ARCH_WANTS_THP_SWAP) && !system_supports_mte();
> >>>>>>> +}
> >>>>>>
> >>>>>> Why ? CONFIG_THP_SWAP depends on ARCH_WANTS_THP_SWAP. In folio_alloc_swap(),
> >>>>>> IS_ENABLED(CONFIG_THP_SWAP) enabled, will also imply ARCH_WANTS_THP_SWAP too
> >>>>>> is enabled. Hence checking for ARCH_WANTS_THP_SWAP again does not make sense
> >>>>>> either in the generic fallback stub, or in arm64 platform override. Because
> >>>>>> without ARCH_WANTS_THP_SWAP enabled, arch_thp_swp_supported() should never
> >>>>>> be called in the first place.
> >>>>>
> >>>>> For the only caller now, the checking looks redundant. But the original
> >>>>> proposed implementation as follows,
> >>>>>
> >>>>> static inline bool arch_thp_swp_supported(void)
> >>>>> {
> >>>>> return true;
> >>>>> }
> >>>>>
> >>>>> will return true even on architectures that don't support/want THP swap.
> >>>>
> >>>> But the function will never be called on for those platforms.
> >>>>
> >>>>> That will confuse people too.
> >>>>
> >>>> I dont see how.
> >>>>
> >>>>>
> >>>>> And the "redundant" checking has no run time overhead, because compiler
> >>>>> will do the trick.
> >>>> I understand that, but dont think this indirection is necessary.
> >>>
> >>> Hi Anshuman, Hi Ying,
> >>> Thanks for the comments of both of you. Does the below look ok?
> >>>
> >>> generic,
> >>>
> >>> static inline bool arch_wants_thp_swap(void)
> >>> {
> >>> return IS_ENABLED(CONFIG_THP_SWAP);
> >>> }
> >>>
> >>> arm64,
> >>>
> >>> static inline bool arch_thp_swp_supported(void)
> >>> {
> >>> return IS_ENABLED(CONFIG_THP_SWAP) && !system_supports_mte();
> >>> }
> >>>
> >>> caller,
> >>>
> >>> folio_alloc_swap(struct folio *folio)
> >>> {
> >>>
> >>> if (folio_test_large(folio)) {
> >>> - if (IS_ENABLED(CONFIG_THP_SWAP))
> >>> + if (arch_thp_swp_supported())
> >>> get_swap_pages(1, &entry, folio_nr_pages(folio));
> >>> goto out;
> >>> }
> >>
> >> Current proposal in this patch LGTM, I dont see any reason for these changes.
> >
> > OK, thanks, Anshuman. Can I collect this as a Reviewed-by?
>
> Yes please.
>
> Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
I've lost track of exactly what the outcome here is, so Barry, please can
you send a final version of the agreed-upon patch?
Thanks,
Will
prev parent reply other threads:[~2022-07-20 9:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 9:00 Barry Song
2022-07-18 16:06 ` Matthew Wilcox
2022-07-18 20:14 ` Barry Song
2022-07-19 0:43 ` Huang, Ying
2022-07-19 1:23 ` Barry Song
2022-07-19 3:08 ` Anshuman Khandual
2022-07-19 3:28 ` Huang, Ying
2022-07-19 3:34 ` Anshuman Khandual
2022-07-19 3:58 ` Huang, Ying
2022-07-19 3:59 ` Barry Song
2022-07-19 4:03 ` Barry Song
2022-07-19 5:46 ` Huang, Ying
2022-07-19 6:13 ` Barry Song
2022-07-19 6:33 ` Huang, Ying
2022-07-19 7:01 ` Barry Song
2022-07-19 7:19 ` Huang, Ying
2022-07-19 8:44 ` Barry Song
2022-07-19 4:03 ` Anshuman Khandual
2022-07-20 1:46 ` Barry Song
2022-07-20 2:36 ` Anshuman Khandual
2022-07-20 9:17 ` Will Deacon [this message]
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=20220720091716.GA15752@willie-the-truck \
--to=will@kernel.org \
--cc=21cnbao@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=guojian@oppo.com \
--cc=hanchuanhua@oppo.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=shy828301@gmail.com \
--cc=steven.price@arm.com \
--cc=v-songbaohua@oppo.com \
--cc=ying.huang@intel.com \
--cc=zhangshiming@oppo.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