From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavu/hashtable: create generic robin hood hash table
Date: Sun, 20 Apr 2025 17:20:08 +0200
Message-ID: <aAUQqMcazFdgpAab@phare.normalesup.org> (raw)
In-Reply-To: <20250420130841.46245-1-emma@emma.gg>
Emma Worley (HE12025-04-20):
> Adds a general purpose hash table with the DXV encoder as an initial use case.
A hash table for flat binary objects of constant size, both keys and
values, does not feel very general-purpose to me. Probably better to
keep it directly in the DXV encoder for now, until other use cases are
found.
(An inventory of all the data structures and algorithms that are
implemented once for a specific component would be nice, though.)
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-20 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 13:08 Emma Worley
2025-04-20 13:08 ` [FFmpeg-devel] [PATCH 2/2] lavc/dxvenc: migrate DXT1 encoder to lavu hashtable and improve Resolume compatibility Emma Worley
2025-04-20 15:10 ` Nicolas George
2025-04-20 15:15 ` James Almer
2025-04-20 15:20 ` Nicolas George [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 5:27 [FFmpeg-devel] [PATCH 1/2] lavu/hashtable: create generic robin hood hash table Connor Worley
2024-02-05 12:00 ` Andreas Rheinhardt
2024-02-06 5:00 ` Connor Worley
2024-02-06 10:13 ` Connor Worley
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=aAUQqMcazFdgpAab@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