Date: Mon, 30 Sep 2002 10:50:03 -0700 (PDT) From: Janos Mohacsi <mohacsi@niif.hu> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/43426: mlockall and munlockall system calls are missing from FreeBSD Message-ID: <200209301750.g8UHo3I8042126@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/43426; it has been noted by GNATS. From: Janos Mohacsi <mohacsi@niif.hu> To: Garrett Wollman <wollman@lcs.mit.edu> Cc: Janos Mohacsi <janos.mohacsi@bsd.hu>, <FreeBSD-gnats-submit@FreeBSD.ORG> Subject: Re: bin/43426: mlockall and munlockall system calls are missing from FreeBSD Date: Mon, 30 Sep 2002 19:45:24 +0200 (CEST) On Fri, 27 Sep 2002, Garrett Wollman wrote: > <<On Fri, 27 Sep 2002 18:18:23 +0200 (CEST), Janos Mohacsi <mohacsi@norfolk.ki.iif.hu> said: > > > The mlockall and munlockall system calls are missing from FreeBSD. > > The mlockall() and munlockall() functions conform to IEEE Std > > 1003.1b-1993 (``POSIX''). FreeBSD should support these system calls. > > FreeBSD-stable does not define _POSIX_MEMLOCK. > FreeBSD-current defines _POSIX_MEMLOCK as -1. > > This indicates to applications that these features are not supported. > > > Try to import from NetBSD. > > FreeBSD and NetBSD have completely different virtual-memory systems. > The functionality would have to be rewritten from scratch. Perhaps > you can interest one of the VM gurus. Yes I knew that, but I expected that mlockall() can be implemented with usage of mlock(), that does exist on FreeBSD. Unfortunately I am not an expert of the VM and I see that mlockall() on NetBSD is working a quite different way than mlock() on FreeBSD. What a pity! Janos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209301750.g8UHo3I8042126>