From: "Rémi Denis-Courmont" <remi@remlab.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v4 2/2][GSoC 2024] tests/checkasm: Add check_vvc_sad to vvc_mc.c Date: Tue, 21 May 2024 08:12:43 +0300 Message-ID: <290D984A-B758-47AC-AEF1-624793FCB13C@remlab.net> (raw) In-Reply-To: <20240520004210.11489-4-chen.stonechen@gmail.com> Hi, Le 20 mai 2024 03:42:03 GMT+03:00, Stone Chen <chen.stonechen@gmail.com> a écrit : >Adds checkasm for DMVR SAD AVX2 implementation. > >Benchmarks ( AMD 7940HS ) >vvc_sad_8x8_c: 70.0 >vvc_sad_8x8_avx2: 10.0 >vvc_sad_16x16_c: 280.0 >vvc_sad_16x16_avx2: 20.0 >vvc_sad_32x32_c: 1020.0 >vvc_sad_32x32_avx2: 70.0 >vvc_sad_64x64_c: 3560.0 >vvc_sad_64x64_avx2: 270.0 >vvc_sad_128x128_c: 13760.0 >vvc_sad_128x128_avx2: 1070.0 >--- > tests/checkasm/vvc_mc.c | 38 ++++++++++++++++++++++++++++++++++++++ > 1 file changed, 38 insertions(+) VVC benchmarks have increased checksam runtime by at least an order of magnitude. It's become so prohibitively slow that I could not even get to the end. This is not an acceptable situation and impedes non-VVC assembler work Please fix this before you add any new VVC tests. In the mean time: -1 / Nack all VVC checksam from my behalf. >diff --git a/tests/checkasm/vvc_mc.c b/tests/checkasm/vvc_mc.c >index 97f57cb401..e251400bfc 100644 >--- a/tests/checkasm/vvc_mc.c >+++ b/tests/checkasm/vvc_mc.c >@@ -322,8 +322,46 @@ static void check_avg(void) > report("avg"); > } > >+static void check_vvc_sad(void) >+{ >+ const int bit_depth = 10; >+ VVCDSPContext c; >+ LOCAL_ALIGNED_32(uint16_t, src0, [MAX_CTU_SIZE * MAX_CTU_SIZE * 4]); >+ LOCAL_ALIGNED_32(uint16_t, src1, [MAX_CTU_SIZE * MAX_CTU_SIZE * 4]); >+ declare_func(int, const int16_t *src0, const int16_t *src1, int dx, int dy, int block_w, int block_h); >+ >+ ff_vvc_dsp_init(&c, bit_depth); >+ memset(src0, 0, MAX_CTU_SIZE * MAX_CTU_SIZE * 4); >+ memset(src1, 0, MAX_CTU_SIZE * MAX_CTU_SIZE * 4); >+ >+ randomize_pixels(src0, src1, MAX_CTU_SIZE * MAX_CTU_SIZE * 2); >+ for (int h = 8; h <= MAX_CTU_SIZE; h *= 2) { >+ for (int w = 8; w <= MAX_CTU_SIZE; w *= 2) { >+ for(int offy = 0; offy <= 4; offy++) { >+ for(int offx = 0; offx <= 4; offx++) { >+ if(check_func(c.inter.sad, "vvc_sad_%dx%d", w, h)) { >+ int result0; >+ int result1; >+ >+ result0 = call_ref(src0 + PIXEL_STRIDE * 2 + 2, src1 + PIXEL_STRIDE * 2 + 2, offx, offy, w, h); >+ result1 = call_new(src0 + PIXEL_STRIDE * 2 + 2, src1 + PIXEL_STRIDE * 2 + 2, offx, offy, w, h); >+ >+ if (result1 != result0) >+ fail(); >+ if(w == h && offx == 0 && offy == 0) >+ bench_new(src0 + PIXEL_STRIDE * 2 + 2, src1 + PIXEL_STRIDE * 2 + 2, offx, offy, w, h); >+ } >+ } >+ } >+ } >+ } >+ >+ report("check_vvc_sad"); >+} >+ > void checkasm_check_vvc_mc(void) > { >+ check_vvc_sad(); > check_put_vvc_luma(); > check_put_vvc_luma_uni(); > check_put_vvc_chroma(); _______________________________________________ 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:[~2024-05-21 5:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-20 0:42 [FFmpeg-devel] [PATCH v4 1/2][GSoC 2024] libavcodec/x86/vvc: Add AVX2 DMVR SAD functions for VVC Stone Chen 2024-05-20 0:42 ` [FFmpeg-devel] [PATCH v4 2/2][GSoC 2024] tests/checkasm: Add check_vvc_sad to vvc_mc.c Stone Chen 2024-05-21 5:12 ` Rémi Denis-Courmont [this message] 2024-05-21 6:37 ` Martin Storsjö 2024-05-21 8:47 ` Rémi Denis-Courmont 2024-05-21 10:12 ` Martin Storsjö 2024-05-21 14:35 ` Ronald S. Bultje 2024-05-20 11:23 ` [FFmpeg-devel] [PATCH v4 1/2][GSoC 2024] libavcodec/x86/vvc: Add AVX2 DMVR SAD functions for VVC Ronald S. Bultje 2024-05-20 15:52 ` Ronald S. Bultje 2024-05-22 0:05 ` Stone Chen -- strict thread matches above, loose matches on Subject: below -- 2024-05-20 0:37 Stone Chen 2024-05-20 0:37 ` [FFmpeg-devel] [PATCH v4 2/2][GSoC 2024] tests/checkasm: Add check_vvc_sad to vvc_mc.c Stone Chen
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=290D984A-B758-47AC-AEF1-624793FCB13C@remlab.net \ --to=remi@remlab.net \ --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