Date: Sun, 17 Oct 2004 11:55:03 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Ben Paley <ben@spooty.net> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Giant and MPSAFE Message-ID: <20041017185503.GC71495@xor.obsecurity.org> In-Reply-To: <200410171238.04809.ben@spooty.net> References: <200410171238.04809.ben@spooty.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--tqI+Z3u+9OQ7kwn0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 17, 2004 at 12:38:04PM +0100, Ben Paley wrote: > Hello, >=20 > bash-2.05b$ uname -a > FreeBSD potato.hogsedge.net 5.3-BETA5 FreeBSD 5.3-BETA5 #0: Mon Sep 20=20 > 07:49:52 BST 2004 root@potato.hogsedge.net:/usr/obj/usr/src/sys/POTAT= O =20 > i386 >=20 > I've just noticed a nasty looking message at boot: >=20 > WARNING: debug.mpsafenet forced to 0 as aio requires Giant > WARNING: MPSAFE network stack disabled, expect reduced performance. >=20 > And then subsequently there are a good few references to things being (fr= om=20 > memory) >=20 > [GIANT LOCKED] >=20 > Anyone have any idea what this is about, and if it's actually bad, and ho= w I=20 > can sort it out? Some subsystems have not yet been modified so they take advantage of multiple processors. aio is one of them, and because it interlinks with the network subsystem, if you have it in your kernel you can't make use of smp in the entire network stack. It's unlikely that you really need aio since it's still experimental code, so you can just compile it out of your kernel. Kris --tqI+Z3u+9OQ7kwn0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBcsAGWry0BWjoQKURArDfAJ9MGaG0AfEQggWrIQ6cQdUE1rSpvQCg1GsQ pfcioTPzZy49sda5QAvkuaQ= =EgLy -----END PGP SIGNATURE----- --tqI+Z3u+9OQ7kwn0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041017185503.GC71495>