From: Arnie Chang <arnie.chang-at-sifive.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/h264chroma: RISC-V V add motion compensation for 4xH and 2xH chroma blocks
Date: Sun, 11 Jun 2023 00:43:52 +0800
Message-ID: <CAPUBFYEKmBiisB6Qc6dv8OV091z9Xw7YqFJ+q7S4bOn2Ynjk-w@mail.gmail.com> (raw)
In-Reply-To: <NX_nV0u--3-9@lynne.ee>
On Sat, Jun 10, 2023 at 10:55 PM Lynne <dev@lynne.ee> wrote:
> Why do they all have the same timing?
>
The processing procedure for these workloads is the same,
except for the difference in block width. (8xH, 4xH, 2xH)
So, the number of instructions remains constant.
Since these workloads handle a small amount of data each time,
the cycle count also stays the same.
However, if the quantity increases, instructions may involve more
micro-operations,
which affects the cycle count (workloads with larger block width may take
more cycles).
_______________________________________________
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:[~2023-06-10 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 7:17 Arnie Chang
2023-06-10 14:55 ` Lynne
2023-06-10 16:43 ` Arnie Chang [this message]
2023-06-12 14:59 ` Rémi Denis-Courmont
2023-06-12 15:28 ` Arnie Chang
2023-06-12 15:29 ` Rémi Denis-Courmont
2023-06-14 15:57 ` Rémi Denis-Courmont
2023-06-15 14:58 ` Arnie Chang
2023-06-15 18:48 ` Rémi Denis-Courmont
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=CAPUBFYEKmBiisB6Qc6dv8OV091z9Xw7YqFJ+q7S4bOn2Ynjk-w@mail.gmail.com \
--to=arnie.chang-at-sifive.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
/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