>>> 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. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
