linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: "guanghui.fgh" <guanghuifeng@linux.alibaba.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	baolin.wang@linux.alibaba.com, catalin.marinas@arm.com,
	akpm@linux-foundation.org, david@redhat.com, jianyong.wu@arm.com,
	james.morse@arm.com, quic_qiancai@quicinc.com,
	christophe.leroy@csgroup.eu, jonathan@marek.ca,
	mark.rutland@arm.com, thunder.leizhen@huawei.com,
	anshuman.khandual@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, geert+renesas@glider.be,
	linux-mm@kvack.org, yaohongbo@linux.alibaba.com,
	alikernel-developer@linux.alibaba.com
Subject: Re: [PATCH v4] arm64: mm: fix linear mem mapping access performance degradation
Date: Tue, 5 Jul 2022 15:56:14 +0300	[thread overview]
Message-ID: <YsQ07kvZX5sO2ov2@kernel.org> (raw)
In-Reply-To: <20220705121115.GB1012@willie-the-truck>

On Tue, Jul 05, 2022 at 01:11:16PM +0100, Will Deacon wrote:
> On Tue, Jul 05, 2022 at 08:07:07PM +0800, guanghui.fgh wrote:
> > 
> > 1.The rodata full is harm to the performance and has been disabled in-house.
> > 
> > 2.When using crashkernel with rodata non full, the kernel also will use non
> > block/section mapping which cause high d-TLB miss and degrade performance
> > greatly.
> > This patch fix it to use block/section mapping as far as possible.
> > 
> > bool can_set_direct_map(void)
> > {
> > 	return rodata_full || debug_pagealloc_enabled();
> > }
> > 
> > map_mem:
> > if (can_set_direct_map() || IS_ENABLED(CONFIG_KFENCE))
> > 	flags |= NO_BLOCK_MAPPINGS | NO_CONT_MAPPINGS;
> > 
> > 3.When rodata full is disabled, crashkernel also need protect(keep
> > arch_kexec_[un]protect_crashkres using).
> > I think crashkernel should't depend on radata full(Maybe other architecture
> > don't support radata full now).
> 
> I think this is going round in circles :/
> 
> As a first step, can we please leave the crashkernel mapped unless
> rodata=full? It should be a much simpler patch to write, review and maintain
> and it gives you the performance you want when crashkernel is being used.

Since we are talking about large systems, what do you think about letting
them set CRASH_ALIGN to PUD_SIZE, then

	unmap(crashkernel);
	__create_pgd_mapping(crashkernel, NO_BLOCK_MAPPINGS);

should be enough to make crash kernel mapped with base pages.
 
> Will

-- 
Sincerely yours,
Mike.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-07-05 12:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 15:57 [PATCH v4] arm64: mm: fix linear mem mapping access performance degradation Guanghui Feng
2022-07-04 10:35 ` Will Deacon
2022-07-04 10:58   ` guanghui.fgh
2022-07-04 11:14     ` Will Deacon
2022-07-04 12:05       ` guanghui.fgh
2022-07-04 13:15         ` Will Deacon
2022-07-04 13:41           ` guanghui.fgh
2022-07-04 14:11           ` guanghui.fgh
2022-07-04 14:23             ` Will Deacon
2022-07-04 14:34               ` guanghui.fgh
2022-07-04 16:38                 ` Will Deacon
2022-07-04 17:09                   ` Ard Biesheuvel
2022-07-05  8:35                     ` Baoquan He
2022-07-05  9:52                     ` Will Deacon
2022-07-05 12:07                       ` guanghui.fgh
2022-07-05 12:11                         ` Will Deacon
2022-07-05 12:27                           ` guanghui.fgh
2022-07-05 12:56                           ` Mike Rapoport [this message]
2022-07-05 13:17                             ` guanghui.fgh
2022-07-05 15:02                           ` Mike Rapoport
2022-07-05 15:34                             ` Catalin Marinas
2022-07-05 15:57                               ` Mike Rapoport
2022-07-05 17:05                                 ` Catalin Marinas
2022-07-05 20:45                                   ` Mike Rapoport
2022-07-06  2:49                                     ` guanghui.fgh
2022-07-06  7:43                                       ` Catalin Marinas
2022-07-06 10:04                                     ` Catalin Marinas
2022-07-06 13:54                                       ` Mike Rapoport
2022-07-06 15:18                                         ` guanghui.fgh
2022-07-06 15:30                                           ` guanghui.fgh
2022-07-06 15:40                                           ` Catalin Marinas
2022-07-07 17:02                                             ` guanghui.fgh
2022-07-08 12:28                                             ` [PATCH RESEND " guanghui.fgh
2022-07-10 13:44                                               ` [PATCH v5] " Guanghui Feng
2022-07-10 14:32                                                 ` guanghui.fgh
2022-07-10 15:33                                                 ` guanghui.fgh
2022-07-18 13:10                                                   ` Will Deacon
2022-07-25  6:46                                                     ` Mike Rapoport
2022-07-05  2:44                   ` [PATCH v4] " guanghui.fgh

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=YsQ07kvZX5sO2ov2@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alikernel-developer@linux.alibaba.com \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=catalin.marinas@arm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=david@redhat.com \
    --cc=geert+renesas@glider.be \
    --cc=guanghuifeng@linux.alibaba.com \
    --cc=james.morse@arm.com \
    --cc=jianyong.wu@arm.com \
    --cc=jonathan@marek.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=quic_qiancai@quicinc.com \
    --cc=thunder.leizhen@huawei.com \
    --cc=will@kernel.org \
    --cc=yaohongbo@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).