From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avutil/aes_ctr: simplify and optimize av_aes_ctr_crypt()
Date: Tue, 1 Apr 2025 17:18:03 +0200
Message-ID: <Z-wDq8UYVsXlCZ3E@phare.normalesup.org> (raw)
In-Reply-To: <20250401151637.2021-1-jamrial@gmail.com>
James Almer (HE12025-04-01):
> Process data in chunks of four or eight bytes, depending on host, instead of one
> at a time.
>
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
> libavutil/aes_ctr.c | 47 ++++++++++++++++++++-------------------------
> 1 file changed, 21 insertions(+), 26 deletions(-)
A commit message where the word “optimize” appears should include a
benchmark.
Regards,
--
Nicolas George
_______________________________________________
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 prev parent reply other threads:[~2025-04-01 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 15:16 James Almer
2025-04-01 15:16 ` [FFmpeg-devel] [PATCH 2/2] avutil/aes_ctr: simplify incrementing the counter James Almer
2025-04-01 15:18 ` Nicolas George [this message]
2025-04-01 15:29 ` [FFmpeg-devel] [PATCH v2 1/2] avutil/aes_ctr: simplify and optimize av_aes_ctr_crypt() James Almer
2025-04-01 17:09 ` [FFmpeg-devel] [PATCH 3/3] avutil/tests/aes_ctr: test more than a single block worth of data James Almer
2025-04-03 20:59 ` [FFmpeg-devel] [PATCH 4/6] avutil/test/aes_ctr: also check the encrypted buffer James Almer
2025-04-03 20:59 ` [FFmpeg-devel] [PATCH 5/6] avutil/tests/aes_ctr: reindent after the previous commit James Almer
2025-04-03 20:59 ` [FFmpeg-devel] [PATCH 6/6] avutil/tests/aes_ctr: also randomize the encryption key James Almer
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=Z-wDq8UYVsXlCZ3E@phare.normalesup.org \
--to=george@nsup.org \
--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