From owner-freebsd-current Wed Apr 8 07:15:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07976 for freebsd-current-outgoing; Wed, 8 Apr 1998 07:15:36 -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 HAA07966 for ; Wed, 8 Apr 1998 07:15:33 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id KAA02721; Wed, 8 Apr 1998 10:12:53 -0400 (EDT) From: Peter Dufault Message-Id: <199804081412.KAA02721@hda.hda.com> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <19980408065541.03335@hydrogen.nike.efn.org> from John-Mark Gurney at "Apr 8, 98 06:55:41 am" To: gurney_j@resnet.uoregon.edu Date: Wed, 8 Apr 1998 10:12:52 -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 > > thanks, I've done it this way... and leached most of the source from > sys/i386/i386/simplelock.s... also, I decided to back port the yield > syscall (note, we now have sched_yield and yield syscalls) to 2.2.1-R > and it works great... Yield sinks you to the bottom of the priorities, which is wrong for the fixed priority flavor schedulers, and may be more aggressive than you want. If someone writes a man page for this they should document this behavior. (IMHO) This should be moved to kern_synch since it modifies the priority. Was this added for compatability with another system? 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