taskThe GNU Hurd - Tasks: task #7050, implement shared barriers,...

 
 

task #7050: implement shared barriers, rwlocks, conds

Submitter:  Samuel Thibault <sthibaul>
Submitted:  Mon 02 Jul 2007 12:15:02 AM UTC
   
 
Category:  The GNU Hurd Should Start On:  Sun 01 Jul 2007 10:00:00 PM UTC
Should be Finished on:  Sun 01 Jul 2007 10:00:00 PM UTC Priority:  * 5 - Normal
Status:  None Privacy:  Public
Assigned to:  None Percent Complete:  50%
Open/Closed:  Open Planned Release:  None
Effort:  0.00
Wiki-like text discussion box: 

sem_open and mutex_init were done, remaining work needed for barriers, rwlocks, conds.
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 01 May 2024 10:45:36 AM UTC, 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 https://buildd.debian.org/status/fetch.php?pkg=postgresql-16&arch=hurd-i386&ver=16.1-1%2Bb1&stamp=1705091712&raw=0

# 2 of 215 tests failed.

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

 Samuel Thibault <sthibaul>
Group administrator
Wed 01 May 2024 09:29:39 AM UTC, comment #2: 

Just to reiterate there is still some interest in getting gnu/hurd+postgres to work.

Unclear if Samuel's comment from 2022 changes things (and went unnoticed), but in early 2023, PostgreSQL removed some code towards GNU/Hurd[2] and IIUC one of the blocking reasons was lack of shared semaphores [1].


* PostgreSQL can't run on GNU/Hurd apparently, for lack of shared sempahores, so who would even know if that works?


Reference:
1. https://www.postgresql.org/message-id/CA%2BhUKGJMNGUAqf27WbckYFrM-Mavy0RKJvocfJU%3DJ2XcAZyv%2Bw%40mail.gmail.com
2. https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d2ea2d310dfdc40328aca5b6c52225de78432e01

 Robins Tharakan <robins>
Tue 15 Feb 2022 09:37:16 PM UTC, comment #1: 

sem_open was done in 749cd2ca7893702f762de9d9852a39973eb044a0
mutex_init was done with the mutex rewrite to gsync

We are still missing it for barriers, rwlocks, conds.

 Samuel Thibault <sthibaul>
Group administrator
Mon 02 Jul 2007 12:15:02 AM UTC, original submission:  

E.g databases like postgresql like using process-shared semaphores and mutexes.  The Hurd should support them.

Samuel Thibault <sthibaul>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by robins (Posted a comment)
  • -email is unavailable- added by sthibaul (Submitted the item)

    •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-05-01 sthibaul Summaryimplement shared semaphores and mutexes, implement sem_open/semget implement shared barriers, rwlocks, conds
        Wiki-like text discussion boxAs 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.
    2022-02-15 sthibaul Percent Complete0% 50%
        Wiki-like text discussion boxAs 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. 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.
    2007-07-02 sthibaul 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.

    Back to the top

    Copyright © 2024 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.13-54b4.
    Corresponding source code