On Thu, Dec 10, 2020 at 12:58:09AM +0100, GSR wrote: > The solution I meant is "try working with less concurrently opened > files" or something similar.
Yes, and that's fundamentally hard without creating races and still maintaining the desired ordering of locate output. updatedb.mlocate tries, and has to do a very complicated dance with chdir() back and forth. It runs into lots of icky cases and has to just silently ignore some errors (with associated races); the only winning move is not to play. > I understand the concept beyond io_uring, > but I have not checked any code, so maybe it can be asked to behave > inside the limits, or the calling code must limit the requests or the > processing of the answers, or maybe something else completly. There's no io_uring in updatedb, so this isn't it. /* Steinar */ -- Homepage: https://www.sesse.net/
