From owner-freebsd-current@FreeBSD.ORG Wed Apr 7 01:17:13 2004 Return-Path: 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 CBC7E16A4CE for ; Wed, 7 Apr 2004 01:17:13 -0700 (PDT) Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 041E043D48 for ; Wed, 7 Apr 2004 01:16:57 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (f579ae1a798172814f2effac953b34e7@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128])i368Ctfv003596; Tue, 6 Apr 2004 03:12:56 -0500 (CDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C38AA5453B; Tue, 6 Apr 2004 01:12:53 -0700 (PDT) Date: Tue, 6 Apr 2004 01:12:52 -0700 From: Kris Kennaway To: Artem Koutchine Message-ID: <20040406081251.GA45600@xor.obsecurity.org> References: <20040406071205.GA2819@frontfree.net> <001f01c41bab$ae842570$0c00a8c0@artem> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <001f01c41bab$ae842570$0c00a8c0@artem> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: Qustion about being "Giant-locked" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 07 Apr 2004 08:17:13 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 06, 2004 at 11:49:20AM +0400, Artem Koutchine wrote: > >> While booting i see many drivers marked > >> as [Giant-locked]. > >> Is being Giant-locked good or bad what are the > >> implications? > >It's not good if you have a computer with multiple processors. >=20 > Well, i do have dual xeon with HT (4 logical CPUs). Is there > any way to fight giant-locked drivers or i just have to wait > until the driver will be rewritten w/o Giant? Or there are > some kernel options to disable Giant lock in the drivers? "Giant lock" isn't a feature that can be enabled or disabled, it indicates that the driver code is not yet ready to be run without Giant. Locking work is a major focus of development in the 5.x branch, but as you can see it's not finished yet. Kris --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAcmaCWry0BWjoQKURAi6hAKDZR7GW3+SVTCaxLHcEeXuAIXEr6wCcDnvQ pRae3detHEFsLXRG4hmbdkE= =3XrR -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/--