Curiously, the patchwork comments there point to kernels << 4.2 being the major cause of the performance regressions brought about by TLE. Was it actually 16.04 customers (on 16.04 kernels) that caused this bug to be opened, or was it that you identified the issue on RedHat and then proposed the patch to all the distros?
We're looking at potentially disabling TLE by default for entirely different reasons (though, still mulling that over), but based on my reading of the patchwork discussion, this patch seems like it shouldn't really be necessary to address performance concerns on a system running 4.4 and higher kernels, as 16.04 is. Certainly, there's the minor concern of people running Ubuntu 16.04 in a chroot or container on top of a much older host kernel, but while that's a configuration that happens to work, it's not one we explicitly support[1] or encourage either. [1] With the notable exception that we support 16.04 containers on 14.04 but, then again, 14.04 has the 4.4 kernel available as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560634 Title: [Ubuntu 16.04.1] Provide a way to dynamically enable lock elision on glibc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1560634/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
