Hi all, My thanks as well to Kamil for raising the question; it's been on my list of things to do for a while. The design of my patch set necessitates the allocation of one eventfd descriptor for each kernel handle (which is, sort of, the Windows equivalent of an fd) associated with a sync object. Some applications can use rather a lot of these; users have regularly run into the default limit of 4096. The 1M number comes from Debian and derivatives, which have this as their default hard limit (and is also the distribution I regularly use). I don't have any familiarity with the kernel or anything about the relevant infrastructure, but I don't see any reason why this would be unreasonable, and not just for my Wine patches specifically. On the other hand, I don't think it's quite necessary to go that high; many people have used a 200k limit, apparently successfully. (One badly misbehaving application, Google Earth VR, has a leak that causes it to allocate at least 300k descriptors, at least while loading, but I think that's the only one we've seen that has a leak on that scale. On the other hand 1M would be enough even for it.) One user reported 16k as being not enough for a more well-behaved game (I think it was Frostpunk); that's the highest lower bound I recall hearing. I've been meaning for a while to bring this up to the kernel itself; I certainly don't think 4096 seems like a reasonable limit these days, and that's not just as far as Wine and my patch set is concerned. ἔρρωσθε, Zeb _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
