af_alg_pull_tsgl(9)
π 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 thedstSGL instead of being released. And listen β the caller must release the buffers indst. 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:
af_alg_alloc_tsgl(9)af_alg_count_tsgl(9)af_alg_free_areq_sgls(9)af_alg_wait_for_wmem(9)af_alg_wmem_wakeup(9)af_alg_wait_for_data(9)af_alg_data_wakeup(9)af_alg_sendmsg(9)af_alg_free_resources(9)af_alg_poll(9)af_alg_alloc_areq(9)af_alg_get_rsgl(9)
π§ A little send-off from me to you: this page lives in./crypto, it's dated October 2026, and it answers toaf_alg_pull_tsgl(9)β under theKernel API Manual, periodt. Now go release those buffers, you icon π π₯
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms