Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Wu Jianhua <toqsxw@outlook.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] 回复:  [PATCH 1/4] avcodec/x86/vvc: add alf filter luma and chroma avx2 optimizations
Date: Wed, 1 May 2024 11:02:10 +0000
Message-ID: <OSZP286MB2173BF753364D7A125A1AAE4CA192@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAFXK13ccO=CnwzFnzcu=cWRjZPPmxmbJZ6KeWqrujX-PQrYCrA@mail.gmail.com>

> 发件人: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> 代表 Nuo Mi <nuomi2021@gmail.com>
> 发送时间: 2024年4月30日 11:03
> 收件人: FFmpeg development discussions and patches
> 主题: Re: [FFmpeg-devel] [PATCH 1/4] avcodec/x86/vvc: add alf filter luma and chroma avx2 optimizations
> 
> On Tue, Apr 30, 2024 at 12:34 AM Andreas Rheinhardt <
> andreas.rheinhardt@outlook.com> wrote:
> 
> > toqsxw@outlook.com:
> > > vvc_alf_filter_chroma_16x12_10_c: 7235.5
> > > vvc_alf_filter_chroma_16x12_10_avx2: 9751.0
> >
> > Are these numbers correct? If so, the avx2 version should not be committed.
> >
> It could be a system turbulence. The data around it appears to be correct.
> 
> Hi Jianhua,
> Maybe you can test it again
> Thank you for the patch, Now we can smoothly play a 4k@60 on a modern i7.
> 

Sure. Will rerun the performance test without other processes with high CPU usage running  and resend the v2.
_______________________________________________
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".

      reply	other threads:[~2024-05-01 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 15:24 [FFmpeg-devel] " toqsxw
2024-04-29 16:19 ` Andreas Rheinhardt
2024-04-30 18:03   ` Nuo Mi
2024-05-01 11:02     ` Wu Jianhua [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=OSZP286MB2173BF753364D7A125A1AAE4CA192@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM \
    --to=toqsxw@outlook.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