From: flow gg <hlefthleft@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 1/9] lavc/vp8dsp: R-V put_vp8_pixels
Date: Sun, 12 May 2024 00:03:22 +0800
Message-ID: <CAEa-L+tR4oa7HwYEqJJpXVuRt53sZScTKt-bmF52ab7ZEVBCiQ@mail.gmail.com> (raw)
In-Reply-To: <8709155.vrFXyRyurE@basile.remlab.net>
Wow, got it
Rémi Denis-Courmont <remi@remlab.net> 于2024年5月11日周六 22:39写道：
> Le maanantaina 6. toukokuuta 2024, 6.38.01 EEST uk7b@foxmail.com a écrit :
> > From: sunyuechi <sunyuechi@iscas.ac.cn>
> >
> > C908:
> > vp8_put_pixels4_c: 78.0
> > vp8_put_pixels4_rvi: 33.7
> > vp8_put_pixels8_c: 278.0
> > vp8_put_pixels8_rvi: 55.0
> > vp8_put_pixels16_c: 999.0
> > vp8_put_pixels16_rvi: 86.7
>
> Actually, I do think that the C compiler is doing a better job.
> On SiFive U74, the figures are horrible:
>
> By time:
> vp8_put_pixels4_c: 0.2
> vp8_put_pixels4_rvi: 10.5
> vp8_put_pixels8_c: 1.0
> vp8_put_pixels8_rvi: 30.0
> vp8_put_pixels16_c: 2.2
> vp8_put_pixels16_rvi: 60.0
>
> By cycles:
> vp8_put_pixels4_c: 84.0
> vp8_put_pixels4_rvi: 3871.0
> vp8_put_pixels8_c: 331.0
> vp8_put_pixels8_rvi: 11281.2
> vp8_put_pixels16_c: 826.0
> vp8_put_pixels16_rvi: 22502.0
>
> Best guess is that the data is not 64-bit aligned, otherwise I can't
> really
> make sense of those figures.
>
> --
> Rémi Denis-Courmont
> http://www.remlab.net/
>
>
>
> _______________________________________________
> 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".
>
_______________________________________________
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:[~2024-05-11 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 3:38 uk7b
2024-05-11 14:39 ` Rémi Denis-Courmont
2024-05-11 16:03 ` flow gg [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=CAEa-L+tR4oa7HwYEqJJpXVuRt53sZScTKt-bmF52ab7ZEVBCiQ@mail.gmail.com \
--to=hlefthleft@gmail.com \
--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