Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Darnley <jdarnley@obe.tv>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] RFC: v210enc optimisations and initial AVX-512
Date: Wed, 26 Oct 2022 15:51:15 +0200
Message-ID: <d24e3c2d-9877-2dff-4b49-c85cfed16df5@obe.tv> (raw)
In-Reply-To: <CAFGUN0oz=0+W2tduWiVN0whryBm9r-DqmEVCsLCcYq8Dx5Pd8Q@mail.gmail.com>

> I guess it could also be scaled to ymm if you're a big Skylake fan :P                                                                                                                                             
> (in which case you'd probably want to reorder the shuffle indices so                                                                                                                                              
> that chroma comes first, i.e. movq [u] + movhps [v] + vinserti32x4[y])

What shuffle or permute did you have in mind when you suggested this for 
Skylake?  Without the permute I'm not sure how the change in ordering 
helps.  Aren't we stuck with data in separate lanes?  I'm probably 
missing something though.
_______________________________________________
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:[~2022-10-26 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  3:41 Kieran Kunhya
2022-10-21 13:57 ` Henrik Gramner
2022-10-26 13:51   ` James Darnley [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=d24e3c2d-9877-2dff-4b49-c85cfed16df5@obe.tv \
    --to=jdarnley@obe.tv \
    --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