batadv_v_elp_get_throughput(9)

📦 version 7.3.1, in nixpkgs unstable

💅 batadv_v_elp_get_throughput(9) — the Kernel API Manual page, bestie edition ✨

okay so real talk, this is a page from the Kernel API Manual and it's about batadv_v_elp_get_throughput — the little function that goes and fetches the throughput towards a neighbour. yes, that's the whole vibe. let's get into it 🫶

🌸 NAME 🌸

batadv_v_elp_get_throughput — get the throughput towards a neighbour 💫

like, literally what it says on the tin. you want the throughput, towards a neighbour, and this function is your girl.

✨ SYNOPSIS ✨

bool batadv_v_elp_get_throughput (struct batadv_hardif_neigh_node *neigh
, u32 *pthroughput );

that's it. that's the whole signature. she's a bool-returning icon and she ate 💅

🎀 ARGUMENTS 🎀

  • neigh — the neighbour for which the throughput has to be obtained 🦋 like, the whole point of the call. this is the neighbour in question, no cap.
  • pthroughput — calculated throughput towards the given neighbour, in multiples of 100kpbs. and yes bestie, the units have lore: a value of '1' equals 0.1Mbps, '10' equals 1Mbps, etc. so do the math accordingly, iykyk 🧮✨

👑 RETURN 👑

returns true when the value behind pthroughput was actually set. periodt. that's the vibe check — true means your pointer got blessed with a real number 💖

🌈 SEE ALSO 🌈

kernel file ./net/batman-adv/bat_v_elp.c, struct batadv_v_metric_queue_entry(9), and honestly the whole friend group:

go read them. they're all main character energy in their own way 🔥

ngl, if pthroughput doesn't get set, you're getting a false back and that's your answer. no extra lore, no secret behaviour — just check the return value, bestie 🙈

that's the page!! source/version is ./net/batman-adv and the date on this beauty is October 2026 — so like, future icon behaviour honestly 💜🎀 mwah, go read the rest of the manual, ily 🫶

📦 where this page comes from