Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com>
To: Kieran Kunhya <kieran618@googlemail.com>
Cc: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] swscale: Neon rgb_to_yuv_half process 32 pixels at a time
Date: Sat, 31 May 2025 10:43:08 +0000
Message-ID: <DBAP193MB09569674ECDF0AD3EDD54E208D60A@DBAP193MB0956.EURP193.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CABGuwEmy_pSeTs7rgTTpKCOpro37kCQbX5w1wMvPxUN-_OjwgA@mail.gmail.com>

Correct. I meant dual issue  https://developer.arm.com/documentation/ddi0460/d/Cycle-Timings-and-Interlock-Behavior/Dual-issue

Best regards,
Dmitriy Kovalenko

On May 31, 2025, at 12:32, Kieran Kunhya <kieran618@googlemail.com> wrote:




On Sat, 31 May 2025, 10:17 Dmitriy Kovalenko, <dmtr.kovalenko@outlook.com<mailto:dmtr.kovalenko@outlook.com>> wrote:
This patch integrates so called double bufferring when we are loading

Nit: I am not sure this is what most people refer to as "double buffering"

Kieran
_______________________________________________
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-31 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250531091631.45342-1-dmtr.kovalenko@outlook.com>
2025-05-31  9:11 ` [FFmpeg-devel] [PATCH 1/2] swscale: rgb_to_yuv neon optimizations Dmitriy Kovalenko
2025-06-05 12:00   ` Martin Storsjö
2025-05-31  9:11 ` [FFmpeg-devel] [PATCH 2/2] swscale: Neon rgb_to_yuv_half process 32 pixels at a time Dmitriy Kovalenko
2025-05-31 10:32   ` Kieran Kunhya via ffmpeg-devel
2025-05-31 10:43     ` Dmitriy Kovalenko [this message]
2025-05-31 12:13       ` Martin Storsjö
2025-05-31 12:21         ` Dmitriy Kovalenko
2025-06-05 12:13   ` Martin Storsjö

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=DBAP193MB09569674ECDF0AD3EDD54E208D60A@DBAP193MB0956.EURP193.PROD.OUTLOOK.COM \
    --to=dmtr.kovalenko@outlook.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.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