__sk_mem_reduce_allocated(9)

💸 __sk_mem_reduce_allocated(9) 💸

okay so bestie, welcome to the Kernel API Manual — we're doing a little memory accounting today and honestly it's giving bookkeeping-but-make-it-chaotic ✨

---

🌸 NAME 🌸

__sk_mem_reduce_allocated — reclaim memory_allocated

like, the whole job is give the memory back 🫶

---

🎀 SYNOPSIS 🎀

void __sk_mem_reduce_allocated (struct sock *sk , int amount );

no cap, that's the whole signature. short and iconic 💅

---

🦋 ARGUMENTS 🦋

• sk — socket. the little guy whose memory situation we're adjusting 🌈
• amount — number of quanta. yes, quanta. plural of quantum. physics-adjacent. we love to see it ⭐

---

💜 DESCRIPTION 💜

Bestie, listen. This one is Similar to __sk_mem_reclaim, but — and this is the whole entire lore — it does not update sk_forward_alloc. That's it. That's the difference. The way that one missing update changes everything 😭

So if you were expecting sk_forward_alloc to get touched? It does not. Not here. Not today. Read the reclaim one for that, iykyk.

fr fr, don't assume this updates sk_forward_alloc — the manpage is so clear about it and we're not gonna pretend otherwise 🙈

---

👑 SEE ALSO 👑

Kernel file ./net/core/sock.c — the source of truth, the main character 💖

• sk_ns_capable(9)
• sk_capable(9)
• sk_net_capable(9)
• sk_set_memalloc(9)
• sk_alloc(9)
• sk_clone(9)
• skb_page_frag_refill(9)
• sk_wait_data(9)
• __sk_mem_raise_allocated(9) — the raise one, the opposite vibe 🔥
• __sk_mem_schedule(9)
• __sk_mem_reclaim(9) — the sibling that DOES touch sk_forward_alloc, go read that one next 🧚

---

and that's the teardown, bestie 🎀 this page lives in ./net/core and it's dated October 2026, from the Kernel API Manual — slay, periodt, go reduce some allocated memory 💅✨🍓