Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Dec 2004 21:46:45 +0800
From:      David Xu <davidxu@freebsd.org>
To:        David Xu <davidxu@freebsd.org>
Cc:        cvs-all@freebsd.org
Subject:   Re: cvs commit: src/sys/sys proc.h syscall.h syscall.mk sysproto.h umtx.h src/sys/kern init_sysent.c kern_umtx.c syscalls.c         syscalls.master
Message-ID:  <41C434C5.2080203@freebsd.org>
In-Reply-To: <200412181252.iBICqjN6052974@repoman.freebsd.org>
References:  <200412181252.iBICqjN6052974@repoman.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
I have a demo program there to explain the shared umtx
feature:
http://people.freebsd.org/~davidxu/umtx_cond.c

David Xu wrote:

>davidxu     2004-12-18 12:52:45 UTC
>
>  FreeBSD src repository
>
>  Modified files:
>    sys/sys              proc.h syscall.h syscall.mk sysproto.h 
>                         umtx.h 
>    sys/kern             init_sysent.c kern_umtx.c syscalls.c 
>                         syscalls.master 
>  Log:
>  1. make umtx sharable between processes, the way is two or more processes
>     call mmap() to create a shared space, and then initialize umtx on it,
>     after that, each thread in different processes can use the umtx same
>     as threads in same process.
>  2. introduce a new syscall _umtx_op to support timed lock and condition
>     variable semantics. also, orignal umtx_lock and umtx_unlock inline
>     functions now are reimplemented by using _umtx_op, the _umtx_op can
>     use arbitrary id not just a thread id.
> 
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41C434C5.2080203>