Bug 206489

Summary: [LFC][Multithreading] Introduce ConcurrentInlineLayoutContext
Product: WebKit Reporter: alan <zalan>
Component: Layout and RenderingAssignee: alan <zalan>
Status: NEW    
Severity: Normal CC: bfulgham, emilio, koivisto, sam, simon.fraser, zalan
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 215087    
Attachments:
Description Flags
Patch
none
Concurrent line ranges none

alan
Reported 2020-01-19 21:36:52 PST
see bug 206158 and bug 205601
Attachments
Patch (6.51 KB, patch)
2020-01-19 21:53 PST, alan 		no flags
DetailsFormatted DiffDiff
Concurrent line ranges (4.02 MB, video/quicktime)
2020-01-20 07:32 PST, alan 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
alan
Comment 1 2020-01-19 21:53:34 PST
Created attachment 388200 [details] Patch
alan
Comment 2 2020-01-20 07:32:28 PST
Created attachment 388241 [details] Concurrent line ranges
alan
Comment 3 2020-01-20 07:53:22 PST
The idea here is that if we identify all the line breaks by pre-scanning the content (provided uniform line height etc), we could split the content into well defined line ranges and run concurrent line layout on them.
alan
Comment 4 2020-01-20 08:04:30 PST
This is very different from bug 206158, where the layout is split at formatting context boundaries. The line line ranges here belong to the same inline formatting context so we always stay within an IFC. These are complementary concepts where we could layout multiple sibling IFCs in background threads in addition to splitting them into line ranges (using even more threads!:)
Sam Weinig
Comment 5 2020-01-20 11:59:12 PST
(In reply to zalan from comment #4) > This is very different from bug 206158, where the layout is split at > formatting context boundaries. The line line ranges here belong to the same > inline formatting context so we always stay within an IFC. These are > complementary concepts where we could layout multiple sibling IFCs in > background threads in addition to splitting them into line ranges (using > even more threads!:) !
Note You need to log in before you can comment on or make changes to this bug.