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: "yunfei_zhou@linux.alibaba.com" <yunfei_zhou@linux.alibaba.com>,
	Zhao Zhili <quinkblack@foxmail.com>
Subject: [FFmpeg-devel] Re: [Question]Inquiry Regarding RISC-V RVV Optimization for HEVC Decoding in FFmpeg
Date: Fri, 14 Nov 2025 12:20:29 +0800
Message-ID: <tencent_F9B25B7E35C9805C34DF3EED57E79C5EE009@qq.com> (raw)
In-Reply-To: <cdf2c9d3-4f97-41b3-a536-55d773d06743.yunfei_zhou@linux.alibaba.com>



> On Nov 14, 2025, at 09:52, yunfei_zhou--- via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
> 
> Hi all,
> I hope this message finds you well.
> My name is Yunfei Zhou, and I am a Software Development Engineer at Alibaba DAMO Academy, where I focus on video coding and decoding optimization.
> We are currently exploring vectorization optimizations for HEVC decoding using the RISC-V Vector Extension (RVV) and are eager to contribute our work to the FFmpeg community. 
> Before proceeding, we would like to understand whether there are any existing or ongoing efforts in this area to avoid duplication and, ideally, align or collaborate with current initiatives.
> Could you kindly share an update on the current status of RISC-V RVV support for HEVC decoding in FFmpeg? Specifically, we’d appreciate any information regarding:
> 
> * 
> Recent developments or patches related to RVV-based HEVC optimizations,

Search RVV on code.ffmpeg.org

https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls?state=open&type=all&labels=&milestone=0&project=0&assignee=0&poster=0&sort=&q=rvv

> 
> * 
> Planned future work in this domain, and
> 
> * 
> Available documentation or resources that could help us better understand the existing codebase and optimization strategies.
> Thank you very much for your time and support. We look forward to contributing to and learning from the FFmpeg community.

General document on contributions
https://www.ffmpeg.org/developer.html#Introduction

I have a simple summary on asm optimization

https://gist.github.com/quink-black/316ac42e0482f4158dd7df3003794576

> Best regards,
> Yunfei Zhou
> Alibaba DAMO Academy
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-11-14  4:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14  1:52 [FFmpeg-devel] " yunfei_zhou--- via ffmpeg-devel
2025-11-14  4:20 ` Zhao Zhili via ffmpeg-devel [this message]
2025-11-14 14:21 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-11-15  2:50   ` [FFmpeg-devel] 回复:Re: " yunfei_zhou--- via ffmpeg-devel
2025-11-15 11:51     ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel

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