On Tue, Jun 08, 2021 at 02:03:50PM +0300, Andrey Semashev wrote: > On 6/8/21 4:25 AM, Nicholas Piggin wrote: > > > > Are shared pthread mutexes using existing pthread APIs that are today > > implemented okay with futex1 system call a good reason to constrain > > futex2 I wonder? Or do we have an opportunity to make a bigger change > > to the API so it suffers less from non deterministic latency (for > > example)? > > If futex2 is not able to cover futex1 use cases then it cannot be viewed as > a replacement. In the long term this means futex1 cannot be deprecated and > has to be maintained. My impression was that futex1 was basically > unmaintainable(*) and futex2 was an evolution of futex1 so that users of > futex1 could migrate relatively easily and futex1 eventually removed. Maybe > my impression was wrong, but I would like to see futex2 as a replacement and > extension of futex1, so the latter can be deprecated at some point. You can never delete a kernel system call, so even if you "deprecate" it, it still needs to be supported for forever. Best of all would be if internally your "futex2" code would replace the "futex1" code so that there is no two different code bases. That would be the only sane way forward, having 2 code bases to work with is just insane. > (*) I use "unmaintainable" in a broad sense here. It exists and works in > newer kernel versions and may receive code changes that are necessary to > keep it working, but maintainers refuse any extensions or modifications of > the code, mostly because of its complexity. Adding additional complexity for no good reason is not a good idea, especially if you are asking others to maintain and support that complexity. Would you want to have to do that work? So what's keeping the futex2 code from doing all that futex1 does so that the futex1 code can be deleted internally? thanks, greg k-h
