Date: Wed, 14 Apr 1999 23:15:58 -0700 From: "David Schwartz" <davids@webmaster.com> To: <alk@pobox.com> Cc: <chat@FreeBSD.ORG> Subject: RE: swap-related problems Message-ID: <000101be8707$6d42ae80$021d85d1@whenever.youwant.to> In-Reply-To: <14101.32737.825891.700729@avalon.east>
next in thread | previous in thread | raw e-mail | index | archive | help
> Okay, so it's not good enough, practically. Let's do better: > How about an mmap-backed fork? Better, IMO, would be a system call you could invoke that would cause all of your process' (current and future) memory to be mmap-backed. This includes all current copy-on-write pages. The call could, of course, fail with an ENOMEM if necessary. This would allow a process to be guaranteed long-term reliable operation so long as it correctly handled all error codes. Though probably nobody would use it, it would also be nice to have a system-level flag to set all processes to default to this mode. Just so that you can say that FreeBSD can be 100% reliable in this respect if you want it to. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000101be8707$6d42ae80$021d85d1>