__sk_mem_raise_allocated(9)

okay bestie, welcome to the page for __sk_mem_raise_allocated(9) from the Kernel API Manual — yes, it's a whole kernel function, and yes, we're gonna understand it. 💅

💖 NAME 💖

__sk_mem_raise_allocated — increase memory_allocated. That's the whole assignment, and it ate. ✨

✨ SYNOPSIS ✨

Here's the signature, copied exactly so nobody comes for me:

int __sk_mem_raise_allocated (struct sock *sk , int size , int amt , int
       kind );

🎀 ARGUMENTS 🎀

• sk — socket. Like, the actual socket, bestie.
• size — memory size to allocate.
• amt — pages to allocate.
• kind — allocation type.

🦋 DESCRIPTION 🦋

So this one is similar to __sk_mem_schedule, but with one very important plot twist: it does not update sk_forward_alloc. Not me pointing that out twice, but it's kind of the whole thing. 😭

Unlike the globally shared limits among the sockets under the same protocol, consuming the budget of a memcg won't have a direct effect on other ones. So be optimistic about memcg's tolerance, and leave the callers to decide whether or not to raise allocated through sk_under_memory_pressure or its variants. That's the vibe check: optimistic about memcg, caller makes the call. 🫶

🌈 SEE ALSO 🌈

Kernel file ./net/core/sock.c — and here's the whole squad, no cap:

• 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_schedule(9)
• __sk_mem_reduce_allocated(9)
• __sk_mem_reclaim(9)

That's the page, bestie 💅. Source/version vibe is ./net/core, the date is October 2026, and this is the __sk_mem_raise_allocated(9) page — go off, king 👑.