From owner-freebsd-current@FreeBSD.ORG Tue Dec 20 16:16:19 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEC6816A41F; Tue, 20 Dec 2005 16:16:19 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E50E43D6D; Tue, 20 Dec 2005 16:16:13 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.12.11) with ESMTP id jBKGGBRS037875; Tue, 20 Dec 2005 08:16:11 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id jBKGGB4l037874; Tue, 20 Dec 2005 08:16:11 -0800 (PST) (envelope-from rizzo) Date: Tue, 20 Dec 2005 08:16:11 -0800 From: Luigi Rizzo To: Suleiman Souhlal Message-ID: <20051220081611.A36159@xorpc.icir.org> References: <20051220032538.A33093@xorpc.icir.org> <43A8166C.9060401@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <43A8166C.9060401@FreeBSD.org>; from ssouhlal@FreeBSD.org on Tue, Dec 20, 2005 at 06:34:20AM -0800 Cc: current@FreeBSD.org Subject: Re: td->td_critnest manipulations do not use atomic_add_int ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2005 16:16:19 -0000 On Tue, Dec 20, 2005 at 06:34:20AM -0800, Suleiman Souhlal wrote: > Hello Luigi, > > Luigi Rizzo wrote: > > as in the subject... i see that td->td_critnest (used to determine > > whether a thread can be preempted or not) is manipulated using > > plain ++ or -- instruction instead of the atomic_add_int(). > > This should be fine as it only gets modified by the current thread. If > an interrupt comes while we are decreasing td_critnest back to 0, then > we just don't get preempted immediately, but at the end of our quantum, > or when someone else tries to preempt us, whichever comes first, which > should be totally harmless. i think that there are still some potential race conditions if the variable is read from another processor to make a decision based on its value. My understanding is that when critical_enter() returns, everything in the system should read td->td_critnest >= 1, which may not be guaranteed by the current implementation (which doesn't have smp locks). There might be similar issues in the 1->0 transition. cheers luigi