From: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com> To: ffmpeg-devel@ffmpeg.org Cc: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com> Subject: [FFmpeg-devel] [PATCH v2 0/2] swscale: neon aarch64 rgb_to_yuv optimizationsj Date: Thu, 29 May 2025 23:34:22 +0200 Message-ID: <DBAP193MB09562973A3E34F3AC3CA98F78D66A@DBAP193MB0956.EURP193.PROD.OUTLOOK.COM> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset=y, Size: 913 bytes --] This is a follow up based on the review feedbakc by Martin Storsjö. I fixed all the identation issues and added post load increment to the all used macros and macroed back all the code that was unmacroed in the previous version. Per the prefetching instructions: They definetely not giving visible difference on a new CPUs like Macbook Pro, but I see a noticable 3-5% performance difference on my tests for the more mobile devices for example IPhone 8 with A11 Bionic CPU or Amazon Fire HD which I am interested especially to optimize for. Per my checkasm tests they are not slowing down nethier macos nor linux arm builds so why not to keep them? Dmitriy Kovalenko (2): swscale: rgb_to_yuv neon optimizations swscale: Neon rgb_to_yuv_half process 32 pixels at a time libswscale/aarch64/input.S | 212 +++++++++++++++++++++++++++---------- 1 file changed, 155 insertions(+), 57 deletions(-) -- 2.49.0 [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2025-05-29 21:38 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=DBAP193MB09562973A3E34F3AC3CA98F78D66A@DBAP193MB0956.EURP193.PROD.OUTLOOK.COM \ --to=dmtr.kovalenko@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