From owner-freebsd-arch@FreeBSD.ORG  Wed Dec 15 01:41:07 2010
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 448111065674;
	Wed, 15 Dec 2010 01:41:07 +0000 (UTC)
	(envelope-from davidxu@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 171DD8FC16;
	Wed, 15 Dec 2010 01:41:07 +0000 (UTC)
Received: from xyf.my.dom (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBF1f36Q009454;
	Wed, 15 Dec 2010 01:41:04 GMT (envelope-from davidxu@freebsd.org)
Message-ID: <4D081CB2.80200@freebsd.org>
Date: Wed, 15 Dec 2010 09:41:06 +0800
From: David Xu <davidxu@freebsd.org>
User-Agent: Thunderbird 2.0.0.24 (X11/20100630)
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
References: <201012101050.45214.jhb@freebsd.org>
	<201012130927.26815.jhb@freebsd.org> <4D06C8B0.1060409@freebsd.org>
	<201012140756.52926.jhb@freebsd.org> <4D081C7C.5040407@freebsd.org>
In-Reply-To: <4D081C7C.5040407@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: arch@freebsd.org, Sergey Babkin <babkin@verizon.net>
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 <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Dec 2010 01:41:07 -0000


> You still don't answer me about how to avoid a time-sharing thread
> holding a critical kernel resource which preempted by a user RT thread,
> and later the RT thread requires the resource, but the time-sharing
> thread has no chance to run because another RT thread is dominating
> the CPU because it is doing CPU bound work, result is deadlock, even if
> you know you trust your RT process, there are many code which were

not

> written by you, 
> 
>