Summary: | bmalloc: page size should be configurable at runtime | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Geoffrey Garen <ggaren> | ||||
Component: | bmalloc | Assignee: | Geoffrey Garen <ggaren> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | barraclough, ggaren, kling, msaboff, sam | ||||
Priority: | P2 | ||||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Geoffrey Garen
2016-03-29 16:09:38 PDT
Created attachment 275146 [details]
Patch
Comment on attachment 275146 [details]
Patch
r=me
Committed r198821: <http://trac.webkit.org/changeset/198821> Comment on attachment 275146 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=275146&action=review > Source/bmalloc/bmalloc/VMAllocate.h:51 > + return sysconf(_SC_PAGESIZE); Would it be worth caching the result here? - or are all interesting uses via Heap? r=me & Ellie Barraclough too. > > Source/bmalloc/bmalloc/VMAllocate.h:51
> > + return sysconf(_SC_PAGESIZE);
>
> Would it be worth caching the result here? - or are all interesting uses via
> Heap?
Hmmm... At first I didn't want to because threads. But I guess we can assume that writing a size_t is atomic.
> r=me & Ellie Barraclough too.
\0/
|