Thread (11 messages) 11 messages, 6 authors, 2024-05-17

Re: [LSF/MM/BPF TOPIC] Reclaiming & documenting page flags

From: Muhammad Usama Anjum <hidden>
Date: 2024-02-17 11:57:31
Also in: bpf, linux-fsdevel, linux-ide, linux-mm, linux-nvme, linux-scsi

On Mon, 2024-01-29 at 04:32 +0000, Matthew Wilcox wrote:
Our documentation of the current page flags is ... not great.  I think
I can improve it for the page cache side of things; I understand the
meanings of locked, writeback, uptodate, dirty, head, waiters, slab,
mlocked, mappedtodisk, error, hwpoison, readahead, anon_exclusive,
has_hwpoisoned, hugetlb and large_remappable.

Where I'm a lot more shaky is the meaning of the more "real MM" flags,
like active, referenced, lru, workingset, reserved, reclaim, swapbacked,
unevictable, young, idle, swapcache, isolated, and reported.

Perhaps we could have an MM session where we try to explain slowly and
carefully to each other what all these flags actually mean, talk about
what combinations of them make sense, how we might eliminate some of
them to make more space in the flags word, and what all this looks like
in a memdesc world.

And maybe we can get some documentation written about it!  Not trying
to nerd snipe Jon into attending this session, but if he did ...
This is great idea. Instead of having a session to write
documentation, we can have a session which would be documentation
itself even if nobody translates it to text.
[thanks to Amir for reminding me that I meant to propose this topic]
  
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help