Re:Getaddrinfo() on glibc calls getenv(), oh boy
by Taniwha on Monday October 16, 2023 @11:28PM
(#37910215)
Yes it's worth remembering that the POSIX base came before threads became commonly available (or even had a standardised API)
[ Parent
| on HN ]
Re:Getaddrinfo() on glibc calls getenv(), oh boy
by thayne on Tuesday October 17, 2023 @01:30AM
(#37910976)
Maybe it is time to replace the POSIX base with something that is better suited to a multi-threaded environemnt.
Re:Getaddrinfo() on glibc calls getenv(), oh boy
by FridgeSeal on Tuesday October 17, 2023 @05:29AM
(#37912499)
I’ll go one further and say that maybe it’s time we had OS’/kernel/API base that isn’t just better suited, but is explicitly designed for the massively multithreaded, ludicrously fast, massively concurrent hardware we have in spades these days.
Alas I am not as OS dev, I have not the skills or understanding to not how to build that, or what this would involve, but I do think it’s clear that what we have at the moment isn’t as well suited as it could be. Io_uring / Direct-IO seem to be better suited though.
Re:Getaddrinfo() on glibc calls getenv(), oh boy
by pjmlp on Tuesday October 17, 2023 @06:08AM
(#37912770)
Which is already happening on non UNIX OSes.
Even on OSes that happen to use the Linux kernel like Android, those that insist on using the NDK and pretend it is like GNU/Linux, beyond the official supported use cases, end up bumping their heads against the wall.