From: "Swinney, Jonathan" <jswinney@amazon.com> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Cc: "Martin Storsjö" <martin@martin.st>, "Clément Bœsch" <u@pkh.me>, "Pop, Sebastian" <spop@amazon.com> Subject: [FFmpeg-devel] [PATCH v2 0/1] lavc/aarch64: add some neon pix_abs functions Date: Thu, 14 Apr 2022 16:22:41 +0000 Message-ID: <679fceeff0bc4fdca9e0fe17412d006c@EX13D07UWB004.ant.amazon.com> (raw) Thanks Martin for the review. I made some updates according to the suggestions you made. I added a checkasm function, but I'm new to the test framework, so it may need some work still. > Would it be beneficial to not do the addv here on each iteration, but > accumulate in v18.8h, and the just do one single addv at the end? I did some testing with this, and it is, indeed, faster, however the problem I ran into is that the bounds for the loop can be higher than the capacity of a 16-bit unsigned integer used for accumulating in v16.8h. With the addv inside the loop, this register can hold the maximum possible value without overflowing before we increase the width of the field with the add instruction. If you have a trick or there are restrictions on the inputs that I am not aware of, let me know. > This version most certainly would be slower indeed. If we could be ok with > doing a bit of overread, the simplest version might be to load e.g. "ld1 > {v4.16b, v5.16b}, [x2]" followed by "ext v5.16b, v4.16b, v5.16b, #1" to > shift it. But doing an overlapping unaligned load probably is fine too. I experimented with these instructions and found that it was marginally faster on Graviton 2, but it was slower on Graviton 3. Graviton 3 has more vector pipelines than Graviton 2 and is therefore a better candidate for video encoding workloads, so I chose to prefer Graviton 3. I didn't test it other chips. Thank you for reviewing the patch! Jonathan Swinney _______________________________________________ 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 reply other threads:[~2022-04-14 16:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-14 16:22 Swinney, Jonathan [this message] 2022-04-15 20:45 ` Martin Storsjö 2022-04-16 20:46 ` 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=679fceeff0bc4fdca9e0fe17412d006c@EX13D07UWB004.ant.amazon.com \ --to=jswinney@amazon.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=martin@martin.st \ --cc=spop@amazon.com \ --cc=u@pkh.me \ /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