From: "Martin Storsjö" <martin@martin.st> To: Krzysztof Pyrkosz via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> Cc: Krzysztof Pyrkosz <ffmpeg@szaka.eu> Subject: Re: [FFmpeg-devel] [PATCH] avutil/aarch64/float_dsp_neon: Refactor ff_vector_fmul_add_neon Date: Sun, 19 Jan 2025 22:57:57 +0200 (EET) Message-ID: <8111ca5d-4d1c-15d2-bd32-e74959c2194f@martin.st> (raw) In-Reply-To: <20250119173259.1533-2-ffmpeg@szaka.eu> On Sun, 19 Jan 2025, Krzysztof Pyrkosz via ffmpeg-devel wrote: > Removed a branch, unrolled loop. Speed increase bumped from 3.95 to 5.60. On what core is that? Please quote the actual output including the absolute numbers. I'm getting much more inconclusive numbers for this one: Before: Cortex A53 A72 A73 A78 vector_fmul_add_neon: 620.0 257.2 624.5 162.8 After: vector_fmul_add_neon: 767.0 259.2 767.5 110.5 This seems to make things quite a lot slower on 2 of these 4 cores. On the A78, I'm getting numbers that look like yours though. So while it makes things better on one kind of core, it also regresses things quite a bit on others, so I'm not quite as convinced about this one. > diff --git a/libavutil/aarch64/float_dsp_neon.S b/libavutil/aarch64/float_dsp_neon.S > index 35e2715b87..0ee5c67b91 100644 > --- a/libavutil/aarch64/float_dsp_neon.S > +++ b/libavutil/aarch64/float_dsp_neon.S > @@ -138,19 +138,21 @@ function ff_vector_fmul_window_neon, export=1 > endfunc > > function ff_vector_fmul_add_neon, export=1 > - ld1 {v0.4s, v1.4s}, [x1], #32 > - ld1 {v2.4s, v3.4s}, [x2], #32 > - ld1 {v4.4s, v5.4s}, [x3], #32 > -1: subs w4, w4, #8 > - fmla v4.4s, v0.4s, v2.4s > - fmla v5.4s, v1.4s, v3.4s > - b.eq 2f > - ld1 {v0.4s, v1.4s}, [x1], #32 > - ld1 {v2.4s, v3.4s}, [x2], #32 > - st1 {v4.4s, v5.4s}, [x0], #32 > - ld1 {v4.4s, v5.4s}, [x3], #32 > - b 1b > -2: st1 {v4.4s, v5.4s}, [x0], #32 > +1: > + ldp q0, q1, [x1], #32 > + ldp q2, q3, [x2], #32 > + ldp q4, q5, [x3], #32 > + fmla v4.4s, v0.4s, v2.4s > + fmla v5.4s, v1.4s, v3.4s > + stp q4, q5, [x0], #32 > + ldp q0, q1, [x1], #32 > + ldp q2, q3, [x2], #32 > + ldp q4, q5, [x3], #32 > + fmla v4.4s, v0.4s, v2.4s > + fmla v5.4s, v1.4s, v3.4s > + stp q4, q5, [x0], #32 > + sub w4, w4, #16 > + cbnz w4, 1b > ret Why do you use sub+cbnz, instead of subs+b.gt? Also, having the cbnz directly follow the sub that updates the register, usually causes stalls on in-order cores; the usual pattern would be to have such a decrement e.g. between the last fmla and the following store. Doing that change, i.e. fmla v4.4s, v0.4s, v2.4s fmla v5.4s, v1.4s, v3.4s + subs w4, w4, #16 stp q4, q5, [x0], #32 - sub w4, w4, #16 - cbnz w4, 1b + b.gt 1b ret has this effect on numbers: Before: Cortex A53 A72 A73 A78 vector_fmul_add_neon: 767.0 259.2 769.5 109.0 After: vector_fmul_add_neon: 751.0 254.5 751.0 109.2 That makes things a little bit better on A53,A72,A73, but it's still overall a notable regression on the A53 and A73. // Martin _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-01-19 20:58 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-01-19 17:33 Krzysztof Pyrkosz via ffmpeg-devel 2025-01-19 20:57 ` Martin Storsjö [this message] 2025-01-23 21:31 ` Krzysztof Pyrkosz via ffmpeg-devel
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=8111ca5d-4d1c-15d2-bd32-e74959c2194f@martin.st \ --to=martin@martin.st \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=ffmpeg@szaka.eu \ /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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git