atom feed20 messages in org.freebsd.freebsd-hackersKernel [memory] tweaking question
FromSent OnAttachments
MattApr 4, 2005 11:43 am 
Devon H. O'DellApr 4, 2005 11:49 am 
Marc OlzheimApr 4, 2005 11:49 am 
Joerg SonnenbergerApr 4, 2005 11:51 am 
Dan NelsonApr 4, 2005 11:55 am 
Mike MeyerApr 5, 2005 4:50 am 
gilles chehadeApr 5, 2005 4:50 am 
Dunceor .Apr 5, 2005 4:50 am 
ra...@redshift.comApr 5, 2005 5:25 am 
Peter JeremyApr 7, 2005 1:36 am 
Stijn HoopApr 7, 2005 1:39 am 
ra...@redshift.comApr 7, 2005 1:50 am 
ra...@redshift.comApr 7, 2005 1:51 am 
Zera William HolladayApr 7, 2005 7:24 am 
Robert WatsonApr 7, 2005 12:08 pm 
Michael ShalayeffJul 7, 2005 12:08 pm 
chatonJul 7, 2005 12:08 pm 
Juan J. MartínezJul 7, 2005 12:10 pm 
Juan J. MartínezJul 7, 2005 12:10 pm 
Mike MeyerJul 8, 2005 12:25 pm 
Subject:Kernel [memory] tweaking question
From:Zera William Holladay (zhol@uic.edu)
Date:Apr 7, 2005 7:24:25 am
List:org.freebsd.freebsd-hackers

On Thu, 7 Apr 2005, Peter Jeremy wrote:

These are all reasonably well documented in sys/conf/NOTES. If you want more detail, try a SystemV-oriented Unix book

Close - they only control SystemV shared memory. Sane shared memory is available via mmap(2). SystemV semaphores are controlled via SEMxxx options. Posix semaphores are listed as 'experimental'.

Is there any chance that POSIX semaphores will be anything other than experimental in the future, or is there no interest? Further, the man page indicates that the FreeBSD, POSIX semaphore implementation is not capable of supporting multiple process semaphores. I saw a similar note on a Linux man page. I think this is a shame, since POSIX semaphores seem to be well designed (from a user point of view) compared to SYSV semaphores, which are a total mess.

-Zera