From: Nicholas Piggin <npiggin@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-mm@kvack.org
Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Zefan Li <lizefan@huawei.com>
Subject: Re: [PATCH v5 5/8] mm: HUGE_VMAP arch support cleanup
Date: Fri, 21 Aug 2020 20:39:39 +1000 [thread overview]
Message-ID: <1598006254.vcbwyiiw9l.astroid@bobo.none> (raw)
In-Reply-To: <9b67b892-9482-15dc-0c1e-c5d5a93a3c91@csgroup.eu>
Excerpts from Christophe Leroy's message of August 21, 2020 3:40 pm:
>
>
> Le 21/08/2020 à 06:44, Nicholas Piggin a écrit :
>> This changes the awkward approach where architectures provide init
>> functions to determine which levels they can provide large mappings for,
>> to one where the arch is queried for each call.
>>
>> This removes code and indirection, and allows constant-folding of dead
>> code for unsupported levels.
>
> I think that in order to allow constant-folding of dead code for
> unsupported levels, you must define arch_vmap_xxx_supported() as static
> inline in a .h
>
> If you have them in .c files, you'll get calls to tiny functions that
> will always return false, but will still be called and dead code won't
> be eliminated. And performance wise, that's probably not optimal either.
Yeah that's true actually, I think I didn't find a good place to add
the prototypes in the arch code but I'll have another look and either
rewrite the changelog or remove it. Although this does get a step closer
at least.
Thanks,
Nick
next prev parent reply other threads:[~2020-08-21 10:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 4:44 [PATCH v5 0/8] huge vmalloc mappings Nicholas Piggin
2020-08-21 4:44 ` [PATCH v5 1/8] mm/vmalloc: fix vmalloc_to_page for huge vmap mappings Nicholas Piggin
2020-08-21 4:44 ` [PATCH v5 2/8] mm: apply_to_pte_range warn and fail if a large pte is encountered Nicholas Piggin
2020-08-21 23:24 ` [mm] 8e63b8bbd7: WARNING:at_mm/memory.c:#__apply_to_page_range kernel test robot
2020-08-22 6:19 ` Nicholas Piggin
2020-08-21 4:44 ` [PATCH v5 3/8] mm/vmalloc: rename vmap_*_range vmap_pages_*_range Nicholas Piggin
2020-08-21 5:45 ` Christoph Hellwig
2020-08-21 4:44 ` [PATCH v5 4/8] lib/ioremap: rename ioremap_*_range to vmap_*_range Nicholas Piggin
2020-08-21 5:45 ` Christoph Hellwig
2020-08-21 4:44 ` [PATCH v5 5/8] mm: HUGE_VMAP arch support cleanup Nicholas Piggin
2020-08-21 5:40 ` Christophe Leroy
2020-08-21 10:39 ` Nicholas Piggin [this message]
2020-08-21 12:43 ` Christophe Leroy
2020-08-21 5:46 ` Christoph Hellwig
2020-08-21 4:44 ` [PATCH v5 6/8] mm: Move vmap_range from lib/ioremap.c to mm/vmalloc.c Nicholas Piggin
2020-08-21 5:46 ` Christoph Hellwig
2020-08-21 5:48 ` Christophe Leroy
2020-08-21 4:44 ` [PATCH v5 7/8] mm/vmalloc: add vmap_range_noflush variant Nicholas Piggin
2020-08-21 4:44 ` [PATCH v5 8/8] mm/vmalloc: Hugepage vmalloc mappings Nicholas Piggin
2020-08-21 7:17 ` kernel test robot
2020-08-21 11:27 ` kernel test robot
2020-08-21 5:47 ` [PATCH v5 0/8] huge " Christophe Leroy
2020-08-21 11:11 ` Nicholas Piggin
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=1598006254.vcbwyiiw9l.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lizefan@huawei.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
all inboxes | Powered by JetHome®