From owner-freebsd-arch@FreeBSD.ORG Fri Dec 17 14:06:43 2010 Return-Path: Delivered-To: arch@freebsd.org Received: from alona.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 57C29106564A; Fri, 17 Dec 2010 14:06:40 +0000 (UTC) (envelope-from davidxu@freebsd.org) Message-ID: <4D0B6E54.2070802@freebsd.org> Date: Fri, 17 Dec 2010 22:06:12 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.21 (X11/20090522) MIME-Version: 1.0 To: John Baldwin References: <201012101050.45214.jhb@freebsd.org> <201012160940.58116.jhb@freebsd.org> <4D0AC3EC.1040701@freebsd.org> <201012170752.06540.jhb@freebsd.org> In-Reply-To: <201012170752.06540.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org, Sergey Babkin Subject: Re: Realtime thread priorities X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 14:06:43 -0000 John Baldwin wrote: > Yes, we do not do priority lending for sleep locks, and to date we never > have. This is not a new problem and moving RT priority higher is not > introducing any _new_ problems. However, it does bring _new_ functionality > that some people need. Just because you don't need it doesn't mean it isn't > important. > > Don't let the perfect be the enemy of the good. > > I guess that your real requirement is preempting at user boundary for static priority thread, however current code does not. I doubt that preempting in kernel path which holding an unknown lock has any visible benefit for your application. Yes, perfect is not the enemy but the goal, isn't mutex with priority propagating for perfect ?