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] avcodec/aarch64/aacencdsp: NEON implementation
Date: Tue, 28 Jan 2025 10:46:37 +0200 (EET)
Message-ID: <8b851b99-5416-b5ed-021-107d22dfaa9d@martin.st> (raw)
In-Reply-To: <Z5fOsRclzTEI4JJ0@superpower>
On Mon, 27 Jan 2025, Krzysztof Pyrkosz via ffmpeg-devel wrote:
> On Sun, Jan 26, 2025 at 01:29:38AM +0200, Martin Storsjö wrote:
>> With the following diff:
>>
>> @@ -40,8 +41,8 @@ function ff_aac_quant_bands_neon, export=1
>> movi v5.4s, 0x80, lsl #24
>> .irp signed,1,0
>> \signed:
>> - subs w3, w3, #4
>> ld1 {v3.4s}, [x2], #16
>> + subs w3, w3, #4
>> fmul v3.4s, v3.4s, v0.s[0]
>> .if \signed
>> ld1 {v4.4s}, [x1], #16
>>
>> I'm getting the following improvement:
>>
>> Before: Cortex A53 A72 A78
>> quant_bands_signed_neon: 5661.0 2383.2 1113.2
>> quant_bands_unsigned_neon: 5401.5 2067.8 811.8
>> After:
>> quant_bands_signed_neon: 5402.5 2385.5 1090.0
>> quant_bands_unsigned_neon: 5145.5 2067.8 809.5
>>
>> No change on the A72 here, but apparently a (very) small improvement on the
>> A78, and a bigger improvement on the A53 as expected.
>>
>> If you don't mind these changes, we could land the change with that tweaked.
>> (I guess the numbers in the commit message could be re-measured, but I'm not
>> sure if they change enough to make much of a difference there, especially on
>> the cores you've measured on.)
>>
>> // Martin
>
> I don't mind these changes, I'm perfectly fine with applying any
> improvements on top of the patch.
> The speeds on A78 and x13s did not change significantly, the initial
> benchmark values can be used.
Ok, great, I've pushed this patch then. Thanks for your contribution!
// 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".
prev parent reply other threads:[~2025-01-28 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 18:58 Krzysztof Pyrkosz via ffmpeg-devel
2025-01-25 23:29 ` Martin Storsjö
2025-01-27 18:21 ` Krzysztof Pyrkosz via ffmpeg-devel
2025-01-28 8:46 ` Martin Storsjö [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=8b851b99-5416-b5ed-021-107d22dfaa9d@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