[Bug 50292] Process-local synchronization objects use private interfaces into the Unix library

WineHQ Bugzilla wine-bugs at winehq.org
Thu Jan 28 12:12:28 CST 2021


https://bugs.winehq.org/show_bug.cgi?id=50292

--- Comment #12 from Zebediah Figura <z.figura12 at gmail.com> ---
(In reply to Jacek Caban from comment #11)
> We can ensure that the cache slot is allocated somewhere in
> NtCreateThreadEx, where we can properly propagate error.

I guess putting a hard limit on the number of threads works too...

> FWIW, we wouldn't need to pop from a middle if we had a separated lists for
> each address. The problem would be lock-free mapping from input address to
> such a single listed list. This could be done, but 64-bit key size makes it
> much less appealing (than, say, 30-bit key for fd cache).

Applying a hash map might help in general. I'm not sure how even separate lists
for each address helps us, though. The waits have an arbitrary timeout, so it'd
still be possible to pop from the middle.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list