From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 22:33:15 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F7231065673 for ; Thu, 19 Jan 2012 22:33:15 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.mail.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id 49A548FC14 for ; Thu, 19 Jan 2012 22:33:15 +0000 (UTC) Received: (qmail 4106 invoked by uid 0); 19 Jan 2012 22:33:06 -0000 Received: from 67.206.162.46 by rms-us015 with HTTP Content-Type: text/plain; charset="utf-8" Date: Thu, 19 Jan 2012 17:33:03 -0500 From: "Dieter BSD" Message-ID: <20120119223304.218280@gmx.com> MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: d/9qbyA03zOlNR3dAHAhtFF+IGRvb0DA Subject: Re: Giant lock gone? 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 22:33:15 -0000 >>> 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. Sigh. I wasn't intending to nitpick, I was confused and curious by the apparient contradiction between "completely remove" and what I saw. 8.2 again: find /usr/src/sys | xargs grep -i giant | wc -l 2018 Skimming though the output of grep, a few are just false positives, but most appear to involve the Giant lock. Perhaps these are all unimportant, I don't know. Apologies to anyone I upset.