From: "Martin Storsjö" <martin@martin.st>
To: Grzegorz Bernacki <gjb@semihalf.com>
Cc: upstream@semihalf.com, jswinney@amazon.com, hum@semihalf.com,
ffmpeg-devel@ffmpeg.org, mw@semihalf.com, spop@amazon.com
Subject: Re: [FFmpeg-devel] [PATCH v2 0/7] arm64 neon implementation for 8bits functions
Date: Tue, 4 Oct 2022 13:56:47 +0300 (EEST)
Message-ID: <da408b78-971d-bfca-adb0-7c5435f1bf49@martin.st> (raw)
In-Reply-To: <20221003141020.3564715-1-gjb@semihalf.com>
On Mon, 3 Oct 2022, Grzegorz Bernacki wrote:
> Changes since v1:
>
> - changed tabs to spaces
> - modified branch instruction in vsse8
> - apply Martin's patches with improved instructions scheduling
>
> Grzegorz Bernacki (4):
> lavc/aarch64: Add neon implementation for pix_abs8 functions.
> lavc/aarch64: Provide neon implementation of nsse8
> lavc/aarch64: Provide optimized implementation of vsse8 for arm64.
> lavc/aarch64: Add neon implementation for vsse_intra8
>
> Martin Storsjö (3):
> aarch64: me_cmp: Improve scheduling in ff_pix_abs8_y2_neon
> aarch64: me_cmp: Fix up the prologue of ff_pix_abs8_xy2_neon
> aarch64: me_cmp: Improve scheduling in vsse_intra8
>
> libavcodec/aarch64/me_cmp_init_aarch64.c | 33 ++
> libavcodec/aarch64/me_cmp_neon.S | 414 +++++++++++++++++++++++
> 2 files changed, 447 insertions(+)
Thanks! This mostly looked good to me.
I had actually meant that you would squash my fixes into your patches,
instead of keeping them as separate ones.
After squashing such changes, it might have been interesting to get
updated benchmarks in those commit messages (the ones that you have from
Graviton 3). However in this case, these changes didn't really make much
difference on out-of-order cores, only on in-order cores, so I guess
there's not that much value in getting updated benchmarks from Graviton 3
in this case.
So I went ahead and squashed those patches (and added co-authored-by lines
where relevant), and pushed them now. 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".
next prev parent reply other threads:[~2022-10-04 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 14:10 Grzegorz Bernacki
2022-10-03 14:10 ` [FFmpeg-devel] [PATCH v2 1/7] lavc/aarch64: Add neon implementation for pix_abs8 functions Grzegorz Bernacki
2022-10-03 14:10 ` [FFmpeg-devel] [PATCH v2 2/7] aarch64: me_cmp: Improve scheduling in ff_pix_abs8_y2_neon Grzegorz Bernacki
2022-10-03 14:10 ` [FFmpeg-devel] [PATCH v2 3/7] aarch64: me_cmp: Fix up the prologue of ff_pix_abs8_xy2_neon Grzegorz Bernacki
2022-10-03 14:10 ` [FFmpeg-devel] [PATCH v2 4/7] lavc/aarch64: Provide neon implementation of nsse8 Grzegorz Bernacki
2022-10-03 14:10 ` [FFmpeg-devel] [PATCH v2 5/7] lavc/aarch64: Provide optimized implementation of vsse8 for arm64 Grzegorz Bernacki
2022-10-03 14:10 ` [FFmpeg-devel] [PATCH v2 6/7] lavc/aarch64: Add neon implementation for vsse_intra8 Grzegorz Bernacki
2022-10-03 14:10 ` [FFmpeg-devel] [PATCH v2 7/7] aarch64: me_cmp: Improve scheduling in vsse_intra8 Grzegorz Bernacki
2022-10-04 10:56 ` Martin Storsjö [this message]
2022-10-04 11:34 ` [FFmpeg-devel] [PATCH v2 0/7] arm64 neon implementation for 8bits functions Grzegorz Bernacki
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=da408b78-971d-bfca-adb0-7c5435f1bf49@martin.st \
--to=martin@martin.st \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=gjb@semihalf.com \
--cc=hum@semihalf.com \
--cc=jswinney@amazon.com \
--cc=mw@semihalf.com \
--cc=spop@amazon.com \
--cc=upstream@semihalf.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
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