Clarifying memory management with page folios
Clarifying memory management with page folios
Posted Mar 19, 2021 16:57 UTC (Fri) by willy (subscriber, #9762)In reply to: Clarifying memory management with page folios by clugstj
Parent article: Clarifying memory management with page folios
Posted Mar 19, 2021 17:01 UTC (Fri)
by clugstj (subscriber, #4020)
[Link] (4 responses)
Posted Mar 19, 2021 17:02 UTC (Fri)
by willy (subscriber, #9762)
[Link] (3 responses)
Posted Mar 19, 2021 17:16 UTC (Fri)
by clugstj (subscriber, #4020)
[Link] (2 responses)
Posted Mar 22, 2021 23:48 UTC (Mon)
by milesrout (subscriber, #126894)
[Link] (1 responses)
Posted Sep 16, 2021 8:10 UTC (Thu)
by ncm (guest, #165)
[Link]
How long that name needs to be depends on the scope of the names.
In C, lacking any mechanism for namespacing, a practical name *often* must be unpleasantly long. That is a fault of the language, not (usually) of the person choosing the name; although some people confuse names with specifications, and so invent stupidly long names.
"Compound_page" is not, in any universe, stupidly long for a C struct tag.
Clarifying memory management with page folios
Clarifying memory management with page folios
Clarifying memory management with page folios
Clarifying memory management with page folios
Clarifying memory management with page folios