Date: Sat, 29 Jun 1996 01:19:58 +0300 (EET DST) From: Jukka Ukkonen <jau@jau.csc.fi> To: hackers@freebsd.com Subject: physical memory addresses & memory locking... Message-ID: <199606282219.BAA23320@jau.csc.fi>
next in thread | raw e-mail | index | archive | help
Hello! In a previous message in which I primarily asked about something else I tried also to ask the following... > What is the most reliable way to select a common memory address > inside the 4.4BSD kernel for an object which has been mmap()ed > as shared by multiple processes? I would like to make pick such > an address so that any processes sharing the same object could > be put sleeping on that very address until some other process > sends a "go ahead" message to them. Maybe the macro vtophys() > from machine/pmap.h would be OK? > Oh yes, you may have guessed it. I am thinking about adding in > the kernel support for semaphores settable by user processes, > including the counting semaphore model from POSIX.4. POSIX.4 > message queues might come practically free with the semaphores, > because I have POSIX.4 shared memory routines already which > combined with the semaphores form the basis for the message > queues anyway. > > It would also be really interesting to know whether anyone from > the mmap() people has been working on the new mlockall(2) and > munlockall(2) stuff that was defined by POSIX.4. Does anyone have any idea about finding the kernel's internal memory addresses when one knows processes' memory addresses or does anyone have anything to say about the mlockall() stuff? Cheers, // jau ------ / Jukka A. Ukkonen, FUNET / Centre for Scientific Computing /__ M.Sc. (sw-eng & cs) Tel: (Home&Fax) +358-0-6215280 / Internet: ukkonen@csc.fi (Work) +358-0-4573208 v Internet: jau@funet.fi (Mobile) +358-400-606671
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606282219.BAA23320>