Date: Mon, 18 Nov 2002 21:33:38 -0500 (EST) From: Daniel Eischen <eischen@pcnet1.pcnet.com> To: Brian Smith <dbsoft@technologist.com> Cc: "current@freebsd.org" <current@FreeBSD.ORG> Subject: Re: Are SysV semaphores thread-safe on CURRENT? Message-ID: <Pine.GSO.4.10.10211182130110.12758-100000@pcnet1.pcnet.com> In-Reply-To: <20021119021821.UQPO397.mail1-0.chcgil.ameritech.net@bbs>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Nov 2002, Brian Smith wrote: > I've been porting an application from Linux to FreeBSD using STABLE, and it appears from looking at the > semaphore code that the SysV semaphores are not thread safe on STABLE. I don't have CURRENT source > code to look at currently. Does anyone know if they are thread-safe in CURRENT? [ I assume you mean semop, semctl, not sema_* or sem_* ] Sure SysV semaphores are thread-safe. When a thread blocks on one, the entire process blocks (no threads run). You won't get any safer than that ;-) -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10211182130110.12758-100000>