zstd_create..._byreference(9)

📦 version 7.3.1, in nixpkgs unstable

💅 zstd_create_ddict_byreference(9) — from the Kernel API Manual, bestie ✨

Okay so picture this: you're deep in kernel-land, you have a decompression dictionary just sitting there in memory, and you're like "do I really need to copy it?" No. No you don't. That's the whole vibe of this page 🎀

🌸 NAME 🌸

zstd_create_ddict_byreference — Create decompression dictionary

Yes it's a lot of underscores, no we don't talk about it 💀

✨ SYNOPSIS ✨

zstd_ddict * zstd_create_ddict_byreference (const void *dict , size_t
dict_size , zstd_custom_mem custom_mem );

That's the whole signature, character for character, don't @ me 🫶

🧚 ARGUMENTS 🧚

  • dict — pointer to the dictionary buffer. Your actual dictionary bytes live here 💖
  • dict_size — size of the dictionary buffer. Gotta tell it how much of that buffer is real ✨
  • custom_mem — memory allocator. You bring your own, it uses it, iconic behavior 👑

🦋 DESCRIPTION 🦋

Note — and this is the part where you listen — this uses dict by reference (ZSTD_dlm_byRef), so dict should be free before zstd_ddict is destroyed.

⚠️ Lowkey critical: by reference means it does not copy your bytes. The dict you passed in has to be free before the zstd_ddict gets destroyed. Do not let it dangle, bestie, that's giving undefined behavior energy 😭

🍓 RETURN 🍓

NULL on error, pointer to decompression dictionary otherwise. That's it. That's the return 💅

🌈 SEE ALSO 🌈

Kernel file ./include/linux/zstd.h, plus the whole zstd fam — all of them, no skips:

Like I said. The whole fam. Read them, love them, cite them 📚💜

Okay that's the page!! Sourced from ./include/linux, dated October 2026, straight out of the Kernel API Manual 🌟 Go forth and not-copy your dictionaries, bestie — remember to free dict before you destroy that zstd_ddict, and slay 💅🎀

📦 where this page comes from