ENUM BLK_ZONE_REPORT_FLAGS(9)
β¨ NAME β¨
enum blk_zone_report_flags β the feature flags of reported zone descriptors π
okay so real quick, bestie, this page lives in the Kernel API Manual, and today we're learning about a lil enum that's basically the mood-ring of zone reporting π
π¦ SYNOPSIS π¦
enum blk_zone_report_flags {
BLK_ZONE_REP_CAPACITY ,
BLK_ZONE_REP_CACHED
};
πΈ Constants πΈ
two constants, two vibes, let's get into it β¨
BLK_ZONE_REP_CAPACITYβ output only. it's saying "hey, the zone descriptors in a zone report have a validcapacityfield" π«Ά like it's valid, no cap.BLK_ZONE_REP_CACHEDβ input only. it's saying the zone report should be generated using cached zone information π and in that case? the implicit open, explicit open and closed zone conditions all get reported with theBLK_ZONE_COND_ACTIVEcondition. the way that one condition just absorbs three whole states, main character energy fr fr π
π SEE ALSO π
- the kernel file
./include/uapi/linux/blkzoned.h enum blk_zone_type(9)enum blk_zone_cond(9)struct blk_zone(9)struct blk_zone_report(9)struct blk_zone_range(9)
go read those next, iykyk πβ¨
okay that's the whole page, bestie, you ate that π this one's coming at you from ./include/uapi/linux, dated October 2026, and it's enum blk_zone_report_flags(9) signing off ππ¦ periodt.
π¦ 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