Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Zhao Zhili via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Zhao Zhili <quinkblack@foxmail.com>
Subject: [FFmpeg-devel] Re: [FFFjo] [FFmpeg/FFmpeg] aarch64/vvc: Optimisations of put_luma_v() functions for 10/12-bit (PR #21148)
Date: Wed, 7 Jan 2026 23:34:35 +0800
Message-ID: <tencent_A66E39E5C119B5A86BF6008D69867D5AAF0A@qq.com> (raw)
In-Reply-To: <FFmpeg/FFmpeg/pulls/21148/comment/21484@code.ffmpeg.org>



> On Jan 7, 2026, at 23:10, Martin Storsjö <code@ffmpeg.org> wrote:
> 
> 
> I don't see the update here in this branch (nor in https://code.ffmpeg.org/george.zaguri/FFmpeg/src/branch/test/put_luma_v) for changing the interleaving for in-order cores?
> 
> For what it's worth; at https://code.ffmpeg.org/mstorsjo/FFmpeg/commits/branch/vvc-put-luma-v I pushed the WIP commit I made for testing this, which gives numbers on A53/A55 as shown above. I don't have newer in-order cores than that to test on. (On macOS, it's not possible to pin threads/processes to a specific core, so I'm not aware of a good way of benchmarking on the Apple Silicon efficiency cores.)
> 
> @sean_mcg does have a machine with A520 and A720 cores though - I'd appreciate if he could benchmark this and give corresponding numbers.
> 
> @sean_mcg : If you have time to help out with this; check out https://code.ffmpeg.org/mstorsjo/FFmpeg/commits/branch/vvc-put-luma-v and the preceding commit, build checkasm, and run it (tests/checkasm/checkasm --bench --test=vvc_mc --bench="put_luma_v_1*"). If you don't have a working setup for allowing user mode access to the cycle counters (i.e. can build and load the kernel module from https://code.videolan.org/janne/arm64-cycle-cnt), you might be able to edit libavutil/aarch64/timer.h and change #if defined(__ANDROID__) || defined(__APPLE__) into #if 1 to choose the slightly worse but more accessible timer register.)
> 
> With that setup in place, we'd want numbers for A520 (and ideally A720 too). You can restrict it to run on a specific core by running taskset -c 4 ./tests/checkasm/checkasm ...where 4 is the number of the core you want to run it on. It might require some testing to figure out which cores are the big ones (A720) and which ones are the small ones (A520). The numbers on A520 should be bigger, as it's a slower core. We're mostly interested in the before/after numbers on A520, but if you can time on A720 as well, that'd be appreciated!
> 

Can we purchase a ARM V9 board for testing, e.g., radxa o6, orange pi 6 ?

[1] https://radxa.com/products/orion/o6/
[2] http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-6-Plus.html
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

           reply	other threads:[~2026-01-07 15:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <FFmpeg/FFmpeg/pulls/21148/comment/21484@code.ffmpeg.org>]

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=tencent_A66E39E5C119B5A86BF6008D69867D5AAF0A@qq.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=quinkblack@foxmail.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