From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 11:16:13 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 600D2106566B for ; Thu, 19 Jan 2012 11:16:13 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 5044B1519A2; Thu, 19 Jan 2012 11:16:12 +0000 (UTC) Message-ID: <4F17FB7A.802@FreeBSD.org> Date: Thu, 19 Jan 2012 03:16:10 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Dieter BSD References: <20120119005820.218250@gmx.com> In-Reply-To: <20120119005820.218250@gmx.com> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Giant lock gone? (was: Re: ...focus, longevity, and lifecycle) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2012 11:16:13 -0000 On 01/18/2012 16:58, Dieter BSD wrote: >> The original goal for 5.0 was to completely remove the Giant lock (and >> do other cool SMP-related stuff). Eventually it was realized that this >> was too big a goal to fully accomplish in 5.0 (albeit too late in the >> process) and the goal was changed to do the basic framework for the new >> SMP model; and lay the groundwork for "some things run under Giant for >> now, and we'll remove it from them ASAP." That actually turned out to >> last through 6, making 7 the realization of what 5.0 was supposed to be. > > So you are saying that the Giant lock was completely removed in 7.0? > > 8.2 says: > > atkbd0: [GIANT-LOCKED] > psm0: [GIANT-LOCKED] Yeah, I think nitpicking minor details about Giant still being used on non-critical drivers is definitely the key to solving the problems that face FreeBSD today. I could have more thoroughly clarified the reality of the when/where/how of Giant but it really wasn't central to my point. -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/