af_alg_pull_tsgl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… af_alg_pull_tsgl β€” the kernel API manual, bestie edition 🌸

Okay so picture this: you're deep in the <pink>Kernel API Manual</pink> and you meet af_alg_pull_tsgl. Her whole personality? Releasing the specified buffers from TX SGL. That's it, that's the gig. Let's get into it 🫢


✨ NAME ✨

af_alg_pull_tsgl β€” Release the specified buffers from TX SGL πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

void af_alg_pull_tsgl (struct sock *sk , size_t used , struct scatterlist *dst );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • sk β€” the socket of the connection to user space. That's your main character right there πŸ‘‘
  • used β€” Number of bytes to pull from TX SGL. Just tell her how many bytes, she'll handle it ✨
  • dst β€” If non-NULL, the buffer is reassigned to the dst SGL instead of being released. And listen β€” the caller must release the buffers in dst. Not optional, bestie, that's on you πŸ’€

🌈 DESCRIPTION 🌈

If dst is non-null, reassign the pages to dst. The caller must release the pages. Like, we're being so serious about this one β€” those pages are your responsibility now 🫢


⭐ SEE ALSO ⭐

Kernel file ./crypto/af_alg.c β€” and honestly the whole friend group showed up:


🧚 A little send-off from me to you: this page lives in ./crypto, it's dated October 2026, and it answers to af_alg_pull_tsgl(9) β€” under the Kernel API Manual, periodt. Now go release those buffers, you icon πŸ’…πŸ”₯
πŸ“¦ where this page comes from