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

 
 

task #7050: implement shared semaphores and mutexes, implement sem_open/semget

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: 

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.

* Mandatory Fields

Add a New Comment Rich Markup
   

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 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 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    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

    Powered by Savane 3.13-f8d8.
    Corresponding source code