[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[task #7050] implement shared barriers, rwlocks, conds

From: Samuel Thibault
Subject: [task #7050] implement shared barriers, rwlocks, conds
Date: Wed, 1 May 2024 06:45:37 -0400 (EDT)

Update of task #7050 (group hurd):

                 Summary: implement shared semaphores and mutexes, implement
sem_open/semget => implement shared barriers, rwlocks, conds
Wiki-like text discussion box: As a starter, maybe sem_open() would be easier,
because it seems like it could map very well to a /servers/sem/ directory
where named semaphores would live.
 => sem_open and mutex_init were done, remaining work needed for barriers,
rwlocks, conds.


Follow-up Comment #3:

As my comment said, shared semaphore in terms of sem_open did get implemented,
with shared memory support, so postgresql can indeed use them. The claim
"PostgreSQL can't run on GNU/Hurd apparently, for lack of shared sempahores
(sic)" is obviously misinformed, and voluntarily breaking the build won't help
for sure.

Help welcome to check what actually is a problem with postgresql on GNU/Hurd,
at least it's really not a lack for shared semaphores, they really are there.

As for a data point, see

# 2 of 215 tests failed.

It doesn't look that broken to me...


Reply to this item at:


Message posté via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]