From owner-freebsd-current Wed Apr 8 15:33:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04500 for freebsd-current-outgoing; Wed, 8 Apr 1998 15:33:29 -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 PAA04441 for ; Wed, 8 Apr 1998 15:33:18 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id SAA03924; Wed, 8 Apr 1998 18:29:59 -0400 (EDT) From: Peter Dufault Message-Id: <199804082229.SAA03924@hda.hda.com> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <199804082148.QAA08206@dyson.iquest.net> from "John S. Dyson" at "Apr 8, 98 04:48:29 pm" To: toor@dyson.iquest.net (John S. Dyson) Date: Wed, 8 Apr 1998 18:29:58 -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 > Well, I don't mind renaming it, but I need it. (Unless sched_yield does > what I need.) sched_yield only does this: > need_resched(); In practice this works the way it should by the spec - it places the current process at the end of any equal priority processes. I've got a regression test that verifies that it works as it should for the fixed priority schedulers. It won't lower the priority so it is different from yield. Can you use "setpriority" to the lowest priority do the same thing as yield does now? (I haven't looked at the source so I don't know if it is changed from the man page) 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