From owner-freebsd-current Wed Mar 8 16:47:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9407337B6F0 for ; Wed, 8 Mar 2000 16:47:27 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115256>; Thu, 9 Mar 2000 11:48:16 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: current lockups In-reply-to: <200003082308.SAA64038@hda.hda.com>; from dufault@hda.com on Thu, Mar 09, 2000 at 10:05:21AM +1100 To: Peter Dufault Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Mar9.114816est.115256@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <00Mar8.103928est.115210@border.alcanet.com.au> <200003082308.SAA64038@hda.hda.com> Date: Thu, 9 Mar 2000 11:48:14 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-09 10:05:21 +1100, Peter Dufault wrote: >There's no difference between rtprio and P1003.1B scheduling other than >the name. rtprio is the same as P1003.1B "SCHED_RR". I wasn't aware of that. >I'd like to remove the rtprio call from ntpd. I think we ought to do >it now before 4.0 ships. Given there is a known a priority inversion bug related to realtime (or idle) scheduling, it would seem wise not to use it in any system utilities. The relevant patch would appear to be (untested): --- /usr/src/usr.sbin/ntp/config.h Tue Feb 1 13:56:05 2000 +++ /tmp/config.h Thu Mar 9 11:46:11 2000 @@ -619,10 +619,10 @@ #define HAVE_RANDOM 1 /* Define if you have the rtprio function. */ -#define HAVE_RTPRIO 1 +/* #undef HAVE_RTPRIO */ /* Define if you have the sched_setscheduler function. */ -#define HAVE_SCHED_SETSCHEDULER 1 +/* #undef HAVE_SCHED_SETSCHEDULER */ /* Define if you have the setlinebuf function. */ #define HAVE_SETLINEBUF 1 Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message