From owner-freebsd-hackers Wed Mar 29 13:41:30 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01237 for hackers-outgoing; Wed, 29 Mar 1995 13:41:30 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA01231 for ; Wed, 29 Mar 1995 13:41:24 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id NAA07601; Wed, 29 Mar 1995 13:40:59 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id NAA00175; Wed, 29 Mar 1995 13:40:59 -0800 Message-Id: <199503292140.NAA00175@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@FreeBSD.org, freebsd-realtime@hda.com Subject: Re: FreeBSD support for realtime systems In-reply-to: Your message of "Wed, 29 Mar 95 19:08:09 +0200." <199503291708.TAA27551@uriah.heep.sax.de> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 29 Mar 1995 13:40:55 -0800 Sender: hackers-owner@FreeBSD.org Precedence: bulk >As Peter Dufault wrote: >> >> There is fixed priority scheduling on FreeBSD - see "rtprio". However, >> there is no way to lock a process in memory to avoid page faults, no >> kernel preemption (other than interrupts), and no way to way to reserve >> resources. > >Ain't it possible to apply mlock(2) to a whole process? mlock() isn't currently supported. It is planned for the future, however. -DG