From owner-freebsd-current@FreeBSD.ORG Fri Oct 5 01:18:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4159016A420 for ; Fri, 5 Oct 2007 01:18:00 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 073AF13C467 for ; Fri, 5 Oct 2007 01:17:59 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l950rnd4007903; Thu, 4 Oct 2007 20:53:49 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Thu, 04 Oct 2007 20:53:50 -0400 (EDT) Date: Thu, 4 Oct 2007 20:53:49 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Jeff Roberson In-Reply-To: <20071004174044.E912@10.0.0.1> Message-ID: References: <20071002165007.D587@10.0.0.1> <20071003110727.411aa2de@pleiades.nextvenue.com> <2155.10.202.77.103.1191443576.squirrel@webmail.superhero.nl> <20071004174044.E912@10.0.0.1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Content-ID: Cc: freebsd-current@freebsd.org, "Gelsema, P \(Patrick\) - FreeBSD" Subject: Re: ULE/yielding patch for testing. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2007 01:18:00 -0000 On Thu, 4 Oct 2007, Jeff Roberson wrote: > > I believe I have fixed this bug in the enclosed patch. It is rooted from > /usr/src/sys so you should cd there to apply it. This doesn't break realtime threads doing a sched_yield() does it? I couldn't easily see how the priority gets set back into the realtime class range. But then, maybe I'm a dummy ;-) -- DE