From owner-freebsd-hackers Sat Aug 1 03:19:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27608 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 03:19:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27603 for ; Sat, 1 Aug 1998 03:19:08 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA13606; Sat, 1 Aug 1998 06:17:06 -0400 (EDT) From: Peter Dufault Message-Id: <199808011017.GAA13606@hda.hda.com> Subject: Re: Using FreeBSD for data acquisition? (long) In-Reply-To: <199807311853.MAA04187@count.timing.com> from Craig Anderson at "Jul 31, 98 12:53:12 pm" To: chanders@timing.com (Craig Anderson) Date: Sat, 1 Aug 1998 06:17:06 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... Should RTP_PRIO_REALTIME help? Does FreeBSD > 3 have realtime features that will help? Is there a problem with > the code or a better approach? I put some fixes in FreeBSD-Current to avoid round robin context switches between equal priority RTP_PRIO_REALTIME processes, and it offers the POSIX interface as well as the RTP_PRIO interface, and I've tested it to see it works as advertised. You could try it and see if it behaves the same. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message