From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v4 1/3] lavc/hashtable: create generic robin hood hash table
Date: Wed, 23 Apr 2025 00:04:48 +0200
Message-ID: <aAgSgPaHKkhRPj-y@phare.normalesup.org> (raw)
In-Reply-To: <CAFQzNw4DkD-+xSoNQ5Uiv7OF8w-Awa4m6SQuq8KSb4y4tAuKyg@mail.gmail.com>
Emma Worley (HE12025-04-22):
> Perhaps I can add a `mode` enum parameter to the FFHashtableContext to
> control behavior? Then we can benchmark different behaviors on a
> per-use-case basis.
For benchmarks, I think #ifdef might be less hassle.
Anyway, I repeat: I do not consider it mandatory, and it probably is
only relevant for larger entries.
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-22 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 7:42 Emma Worley
2025-04-22 7:42 ` [FFmpeg-devel] [PATCH v4 2/3] lavc/dxvenc: migrate DXT1 encoder to lavc hashtable Emma Worley
2025-04-22 7:42 ` [FFmpeg-devel] [PATCH v4 3/3] lavc/dxvenc: improve compatibility with Resolume products Emma Worley
2025-04-22 7:59 ` Andreas Rheinhardt
2025-04-22 8:14 ` Emma Worley
2025-04-22 17:24 ` [FFmpeg-devel] [PATCH v4 1/3] lavc/hashtable: create generic robin hood hash table Nicolas George
2025-04-22 17:57 ` Emma Worley
2025-04-22 22:04 ` Nicolas George [this message]
2025-04-22 22:02 ` Nicolas George
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=aAgSgPaHKkhRPj-y@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