RESOLVED FIXED 284338
Allocate megapages from different page provider than large allocations in libpas 
https://bugs.webkit.org/show_bug.cgi?id=284338
Summary Allocate megapages from different page provider than large allocations in libpas
David Degazio
Reported 2024-12-09 16:30:20 PST
rdar://138070544 Currently libpas self-hosts when claiming space for small and medium objects - objects of these sizes are allocated out of megapages, and those megapages are themselves allocated using a large heap, internally indistinguishable from other large objects. This is kind of graceful, but also a little bit limiting, because there's no way to tell at the mapping level whether a page allocation contains a diversity of small or medium pages with different size classes, or a single huge allocation occupying a multi-page range. To more easily break down the way pages are used by different sizes of objects, we can separate out the page providers for these categories, giving megapages (and hence all small/medium objects within them) a distinct large free heap from which their memory ultimately originates.
Attachments
Add attachment proposed patch, testcase, etc.
David Degazio
Comment 1 2024-12-09 16:55:47 PST
Pull request: https://github.com/WebKit/WebKit/pull/37676
EWS
Comment 2 2024-12-18 17:25:17 PST
Committed 288057@main (968212ccdd07): <https://commits.webkit.org/288057@main> Reviewed commits have been landed. Closing PR #37676 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.