obj_cgroup_charge_zswap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… obj_cgroup_charge_zswap(9) β€” the Kernel API Manual situation

okay so bestie, welcome to the obj_cgroup_charge_zswap(9) page πŸŽ€ this is a Kernel API Manual moment, and honestly? it's short, it's sweet, it does exactly one thing. main character energy fr fr.


✨ NAME ✨

obj_cgroup_charge_zswap β€” charge compression backend memory 🧚


🌸 SYNOPSIS 🌸

void obj_cgroup_charge_zswap (struct obj_cgroup *objcg , size_t size );

that's it. that's the whole signature. void in, void out, no takebacks. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • objcg β€” the object cgroup πŸ‘‘ like, the cgroup in question, the one we're doing all this for.
  • size β€” size of compressed object πŸ“ yes bestie, we're talking about the compressed one specifically.

πŸ’– DESCRIPTION πŸ’–

so here's the tea β˜• this function forces the charge. like, no more asking nicely, the charge is happening.

but context matters, so let me set the scene: obj_cgroup_may_zswap has to have already allowed compression and storage in zswap for this cgroup to go ahead. that's the green light, that's the vibe check that passed. once that's done, obj_cgroup_charge_zswap comes in and makes the charge actually go through. periodt. πŸ”₯

ngl that's genuinely the whole description. no cap, that's it. don't go looking for a hidden paragraph, there isn't one πŸ™ˆ

πŸ’œ SEE ALSO πŸ’œ

okay this is the part where the manpage goes absolutely feral with cross-references 😭 like, grab a snack, this list is long. every single one of these is a (9) situation:

also, for the record, the kernel file is ./mm/memcontrol.c β€” that's where this lives, iykyk 🌈

and deadass, the natural follow-ups here are obj_cgroup_may_zswap(9) (the permission slip) and obj_cgroup_uncharge_zswap(9) (the undo button), so if you're reading this page you're probably reading those too 🫢


⭐ the sign-off ⭐

this whole thing comes courtesy of ./mm, dated October 2026, and it's filed under obj_cgroup_charge_zswap(9) β€” so if you memorise one thing today, memorise that it charges compression backend memory, and that it's the forceful follow-up to obj_cgroup_may_zswap saying yes πŸ’€βœ¨ slay, go charge something, bestie πŸ’…πŸŒΈ

πŸ“¦ where this page comes from