(In reply to comment #14)
> the increased size should only matter if the new size pushes past a page
> boundary right ? and even then, it'd only be 4KiB per thread ?
>
> i don't see that being a problem.
No the new size is going to be the full size of the PT_TLS segment e.g. static .tdata/.tbss which is normally allocated out of the thread stack.
Could you do a canvas of a gentoo install to see how big those TLS segments are in executables?
e.g.
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
...
TLS 0x185194 0x00186194 0x00186194 0x00008 0x00040 R 0x4
...
(In reply to comment #14)
> the increased size should only matter if the new size pushes past a page
> boundary right ? and even then, it'd only be 4KiB per thread ?
>
> i don't see that being a problem.
No the new size is going to be the full size of the PT_TLS segment e.g. static .tdata/.tbss which is normally allocated out of the thread stack.
Could you do a canvas of a gentoo install to see how big those TLS segments are in executables?
e.g.
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
...
TLS 0x185194 0x00186194 0x00186194 0x00008 0x00040 R 0x4
...
The reservations grow by MemSiz.