On 04/05/2016 06:47 PM, Peter Zijlstra wrote: > On Tue, Apr 05, 2016 at 06:02:25PM +0200, Florian Weimer wrote: >> On 04/04/2016 10:48 PM, Mathieu Desnoyers wrote: >> >>> Moreover, the feature set that the application knows about, glibc >>> knows about, and the kernel knows about are three different things. >>> My intent here is to have glibc stay out of the way as much as possible, >>> since this is really an interface between various applications/libraries >>> and the kernel. >> >> Surely glibc can allocate the space based on what is advertised as >> needed by the kernel? Why would it limit itself to what is supported by >> the kernel headers it is compiled against if the actual size can be >> queried from the kernel? > > I guess the question is; can we do thread local variable arrays like: > > __thread uint32_t[x]; /* with x being a runtime constant */ > > Because then we can do: > > __thread struct thread_local_abi tla; > > where sizeof(struct thread_local_abi) is a runtime variable. It's slightly complicated. ELF TLS in the GNU ABI will give you a static offset only with static linking. > Without that we cannot have this thread-local-abi structure be part of > the immediately addressable TLS space. That is, we then need a pointer > like: > > __thread struct thread_local_abi *tla; > > and every usage will need the extra pointer deref. The offset relative to the base will be dynamic anyway and need an extra load (which can be hoisted out of loops etc., but it's still there in some case). > Because ideally this structure would be part of the initial (glibc) TCB > with fixed offset etc. This is not possible because we have layering violations and code assumes it knows the precise of the glibc TCB. I think Address Sanitizer is in this category. This means we cannot adjust the TCB size based on the kernel headers used to compile glibc, and there will have to be some indirection. Florian -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
