From: "Martin Storsjö" <martin@martin.st>
To: "Swinney, Jonathan" <jswinney@amazon.com>
Cc: "Clément Bœsch" <u@pkh.me>, "Pop, Sebastian" <spop@amazon.com>,
"FFmpeg development discussions and patches"
<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] swscale: aarch64: Optimize the final summation in the hscale routine
Date: Fri, 22 Apr 2022 10:50:50 +0300 (EEST)
Message-ID: <b4baa5d-234c-ac22-28c-6472a9278e5@martin.st> (raw)
In-Reply-To: <3BEA4526-3C82-4CE5-870A-D8155C29495C@amazon.com>
On Thu, 21 Apr 2022, Swinney, Jonathan wrote:
> Thanks for making this improvement. I will rebase my patches on your change. I also measured the performance on AWS Graviton 2 and 3. I added the numbers to your table.
>
> Before: Cortex A53 A72 A73 Graviton 2 Graviton 3
> hscale_8_to_15_width8_neon: 8273.0 4602.5 4289.5 2429.7 1629.1
> hscale_8_to_15_width16_neon: 12405.7 6803.0 6359.0 3549.0 2378.4
> hscale_8_to_15_width32_neon: 21258.7 11491.7 11469.2 5797.2 3919.6
> hscale_8_to_15_width40_neon: 25652.0 14173.7 12488.2 6893.5 4810.4
>
> After:
> hscale_8_to_15_width8_neon: 7633.0 3981.5 3350.2 1980.7 1261.1
> hscale_8_to_15_width16_neon: 11666.7 5951.0 5512.0 3080.7 2131.4
> hscale_8_to_15_width32_neon: 20900.7 10733.2 9481.7 5275.2 3862.1
> hscale_8_to_15_width40_neon: 24826.0 13536.2 11502.0 6397.2 4731.9
Thanks for the benchmarks! I pushed this patch now, with those numbers
included.
// 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:[~2022-04-22 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 8:57 Martin Storsjö
2022-04-21 21:43 ` Swinney, Jonathan
2022-04-22 7:50 ` 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=b4baa5d-234c-ac22-28c-6472a9278e5@martin.st \
--to=martin@martin.st \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=jswinney@amazon.com \
--cc=spop@amazon.com \
--cc=u@pkh.me \
/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