linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Kai Shen <shenkai8@huawei.com>
Cc: will@kernel.org, linux-arm-kernel@lists.infradead.org,
	LKML <linux-kernel@vger.kernel.org>,
	xuwei5@hisilicon.com, hewenliang4@huawei.com, wuxu.wu@huawei.com
Subject: Re: [PATCH] arm64:align function __arch_clear_user
Date: Wed, 14 Apr 2021 11:41:44 +0100	[thread overview]
Message-ID: <20210414104144.GB8320@arm.com> (raw)
In-Reply-To: <58fecb22-f932-cb6e-d996-ca75fe26a75d@huawei.com>

On Wed, Apr 14, 2021 at 05:25:43PM +0800, Kai Shen wrote:
> Performance decreases happen in __arch_clear_user when this
> function is not correctly aligned on HISI-HIP08 arm64 SOC which
> fetches 32 bytes (8 instructions) from icache with a 32-bytes
> aligned end address. As a result, if the hot loop is not 32-bytes
> aligned, it may take more icache fetches which leads to decrease
> in performance.
> Dump of assembler code for function __arch_clear_user:
>        0xffff0000809e3f10 :    nop
>        0xffff0000809e3f14 :    mov x2, x1
>        0xffff0000809e3f18 :    subs x1, x1, #0x8
>        0xffff0000809e3f1c :    b.mi 0xffff0000809e3f30 <__arch_clear_user+3
> -----  0xffff0000809e3f20 :    str    xzr, [x0],#8
> hot    0xffff0000809e3f24 :    nop
> loop   0xffff0000809e3f28 :    subs x1, x1, #0x8
> -----  0xffff0000809e3f2c :    b.pl  0xffff0000809e3f20 <__arch_clear_user+1
> The hot loop above takes one icache fetch as the code is in one
> 32-bytes aligned area and the loop takes one more icache fetch
> when it is not aligned like below.
>        0xffff0000809e4178 :   str    xzr, [x0],#8
>        0xffff0000809e417c :   nop
>        0xffff0000809e4180 :   subs x1, x1, #0x8
>        0xffff0000809e4184 :   b.pl  0xffff0000809e4178 <__arch_clear_user+
> Data collected by perf:
>                          aligned   not aligned
>           instructions   57733790     57739065
>        L1-dcache-store   14938070     13718242
> L1-dcache-store-misses     349280       349869
>        L1-icache-loads   15380895     28500665
> As we can see, L1-icache-loads almost double when the loop is not
> aligned.
> This problem is found in linux 4.19 on HISI-HIP08 arm64 SOC.
> Not sure what the case is on other arm64 SOC, but it should do
> no harm.
> Signed-off-by: Kai Shen <shenkai8@huawei.com>

Do you have a real world workload that's affected by this function?

I'm against adding alignments and nops for specific hardware
implementations. What about lots of other loops that the compiler may
generate or that we wrote in asm?

-- 
Catalin

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

       reply	other threads:[~2021-04-14 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <58fecb22-f932-cb6e-d996-ca75fe26a75d@huawei.com>
2021-04-14 10:41 ` Catalin Marinas [this message]
2021-04-19  2:05   ` [PATCH] arm64:align function __arch_clear_user Kai Shen
2021-04-23 15:37     ` Catalin Marinas
2021-04-25  2:07       ` Kai Shen
2021-04-27 16:50         ` Robin Murphy

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=20210414104144.GB8320@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=hewenliang4@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shenkai8@huawei.com \
    --cc=will@kernel.org \
    --cc=wuxu.wu@huawei.com \
    --cc=xuwei5@hisilicon.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).