From owner-freebsd-hackers  Wed Jun  7 20:20:52 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id UAA29315
          for hackers-outgoing; Wed, 7 Jun 1995 20:20:52 -0700
Received: from hq.icb.chel.su (icb-rich-gw.icb.chel.su [193.125.10.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA29307
          for <hackers@freebsd.org>; Wed, 7 Jun 1995 20:20:19 -0700
Received: from localhost (babkin@localhost) by hq.icb.chel.su (8.6.5/8.6.5) id IAA11644; Thu, 8 Jun 1995 08:50:15 +0500
From: "Serge A. Babkin" <babkin@hq.icb.chel.su>
Message-Id: <199506080350.IAA11644@hq.icb.chel.su>
Subject: Re: Interval timer/System clock
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 8 Jun 1995 08:50:14 +0500 (GMT+0500)
Cc: hackers@freebsd.org
In-Reply-To: <199506071237.WAA17067@godzilla.zeta.org.au> from "Bruce Evans" at Jun 7, 95 10:37:47 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 417       
Sender: hackers-owner@freebsd.org
Precedence: bulk

> the others at rtprio 0.  I think the priority doesn't affect swapping,
> so for consistent timing a real time process might want extra wakeups to
> keep itself in core and early wakeups to allow time for swapping it in;

Does mlock() not work in FreeBSD ? Or does it not help in this case ?

		Serge Babkin

! (babkin@hq.icb.chel.su)
! Headquarter of Joint Stock Commercial Bank "Chelindbank"
! Chelyabinsk, Russia