From owner-freebsd-current Wed Apr 8 04:57:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21165 for freebsd-current-outgoing; Wed, 8 Apr 1998 04:57:00 -0700 (PDT) (envelope-from owner-freebsd-current@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 EAA21160 for ; Wed, 8 Apr 1998 04:56:56 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA02444; Wed, 8 Apr 1998 07:53:59 -0400 (EDT) From: Peter Dufault Message-Id: <199804081153.HAA02444@hda.hda.com> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <199804072257.RAA26476@detlev.UUCP> from Joel Ray Holveck at "Apr 7, 98 05:57:15 pm" To: joelh@gnu.org Date: Wed, 8 Apr 1998 07:53:59 -0400 (EDT) Cc: current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> No, you'd go to sleep for a jiffy and check again... I belive a > >> yield() syscall is in the pipeline or maybe already in. > > Yield is in the kernel. > > Is yield() the same as sleep(0)? No, in that the behavior is standard. "man sched_yield" on current. At least for now you need: options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" 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-current" in the body of the message