Mathieu Desnoyers wrote: > If we invoke this per-thread registration directly in the glibc NPTL implementation, > in start_thread, do you think it would fit your requirements ? I guess this would basically be transparent to the user -- we'd just need to make sure that the registration happens very early, before any chance of calling malloc. That said, having the ability for the kernel to understand that TLS implementation are laid out using the same offset on each thread seems like something that could be valuable long term. Doing so makes it possible to build other TLS-based features without forcing each thread to be registered. -- 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
